<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Setting cluster settings through SCIM in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/setting-cluster-settings-through-scim/m-p/21602#M14745</link>
    <description>&lt;P&gt;&lt;B&gt;Credential passthrough&lt;/B&gt;&lt;/P&gt;&lt;P&gt;This actually needs some setting up in AWS IAM to get started. Once you've created the right instance profiles, you'll need to add them to your Databricks workspace. There's pretty exhaustive guides here that has each of the steps. &lt;/P&gt;&lt;P&gt;AWS: &lt;A href="https://docs.databricks.com/security/credential-passthrough/iam-passthrough.html" target="test_blank"&gt;https://docs.databricks.com/security/credential-passthrough/iam-passthrough.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Azure: &lt;A href="https://docs.microsoft.com/en-us/azure/databricks/security/credential-passthrough/adls-passthrough" target="test_blank"&gt;https://docs.microsoft.com/en-us/azure/databricks/security/credential-passthrough/adls-passthrough&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Single user access&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Do you mean restricting access to a cluster for a single user? You can't directly do this with only SCIM APIs. You'll need to utilize the permissions API to set which users can attach to/run/manage a cluster and simply restrict that to a single user or group.&lt;/P&gt;&lt;P&gt;The SCIM APIs allow you to set whether that user is part of a particular group or whether they can access the Databricks DE/DS or SQL analytics workspace in the first place. It also allows you to specify if someone has global cluster creation/editing privileges.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Permission settings&lt;/B&gt;&lt;/P&gt;&lt;P&gt;See above, you might want to look at the permissions API. &lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/dev-tools/api/latest/permissions.html" target="test_blank"&gt;https://docs.databricks.com/dev-tools/api/latest/permissions.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Heads up some of the advanced permissions settings also need to be enabled by logging in, going to the Admin console from the dropdown in the top right, and then 'Workspace Settings' tab at the top.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jun 2021 17:36:16 GMT</pubDate>
    <dc:creator>Taha</dc:creator>
    <dc:date>2021-06-23T17:36:16Z</dc:date>
    <item>
      <title>Setting cluster settings through SCIM</title>
      <link>https://community.databricks.com/t5/data-engineering/setting-cluster-settings-through-scim/m-p/21601#M14744</link>
      <description>&lt;P&gt;is there a way to set the following cluster settings through the SCIM? I am not seeing anything in the API docs that would suggest it is possible but I want to double check here.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Enable credential passthrough&lt;/LI&gt;&lt;LI&gt;Single User Access&lt;/LI&gt;&lt;LI&gt;Permission settings&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 01:14:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/setting-cluster-settings-through-scim/m-p/21601#M14744</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2021-06-23T01:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: Setting cluster settings through SCIM</title>
      <link>https://community.databricks.com/t5/data-engineering/setting-cluster-settings-through-scim/m-p/21602#M14745</link>
      <description>&lt;P&gt;&lt;B&gt;Credential passthrough&lt;/B&gt;&lt;/P&gt;&lt;P&gt;This actually needs some setting up in AWS IAM to get started. Once you've created the right instance profiles, you'll need to add them to your Databricks workspace. There's pretty exhaustive guides here that has each of the steps. &lt;/P&gt;&lt;P&gt;AWS: &lt;A href="https://docs.databricks.com/security/credential-passthrough/iam-passthrough.html" target="test_blank"&gt;https://docs.databricks.com/security/credential-passthrough/iam-passthrough.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Azure: &lt;A href="https://docs.microsoft.com/en-us/azure/databricks/security/credential-passthrough/adls-passthrough" target="test_blank"&gt;https://docs.microsoft.com/en-us/azure/databricks/security/credential-passthrough/adls-passthrough&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Single user access&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Do you mean restricting access to a cluster for a single user? You can't directly do this with only SCIM APIs. You'll need to utilize the permissions API to set which users can attach to/run/manage a cluster and simply restrict that to a single user or group.&lt;/P&gt;&lt;P&gt;The SCIM APIs allow you to set whether that user is part of a particular group or whether they can access the Databricks DE/DS or SQL analytics workspace in the first place. It also allows you to specify if someone has global cluster creation/editing privileges.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Permission settings&lt;/B&gt;&lt;/P&gt;&lt;P&gt;See above, you might want to look at the permissions API. &lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/dev-tools/api/latest/permissions.html" target="test_blank"&gt;https://docs.databricks.com/dev-tools/api/latest/permissions.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Heads up some of the advanced permissions settings also need to be enabled by logging in, going to the Admin console from the dropdown in the top right, and then 'Workspace Settings' tab at the top.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 17:36:16 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/setting-cluster-settings-through-scim/m-p/21602#M14745</guid>
      <dc:creator>Taha</dc:creator>
      <dc:date>2021-06-23T17:36:16Z</dc:date>
    </item>
  </channel>
</rss>

