<?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 Store a secret only accessible to the current user in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/store-a-secret-only-accessible-to-the-current-user/m-p/23056#M1301</link>
    <description>&lt;P&gt;During an interactive notebook session, I want a user to be able to retrieve a secret specific to that user. I haven't decided on storage mechanisms, but I'm open to storage mechanisms that can scalably authorize access to a single user and that I can write the secret from an external service. I have looked into the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/secret-acl.html" alt="https://docs.databricks.com/security/access-control/secret-acl.html" target="_blank"&gt;Databricks Secrets&lt;/A&gt;: with a limit of 100 scopes, this does not scale beyond 100 users and I work in an engineering organization with over 200 people&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/credential-passthrough/index.html" alt="https://docs.databricks.com/security/credential-passthrough/index.html" target="_blank"&gt;IAM credential passthrough&lt;/A&gt;: does not support MLFlow (my data science team uses MLFlow), and according to my reading it does not support non-admin users calling Scala (I have at least one team that requires the use of Scala)&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/table-acls/index.html" alt="https://docs.databricks.com/security/access-control/table-acls/index.html" target="_blank"&gt;Table Access Control&lt;/A&gt;: I could use this to create a view that is limited to results matching CURRENT_USER, but won't work for users who need to use Scala&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/workspace-acl.html" alt="https://docs.databricks.com/security/access-control/workspace-acl.html" target="_blank"&gt;Workspace object access control&lt;/A&gt;: it has an API I can use to write secrets, and I can limit access by user. I would prefer if I can prevent admins from reading the secret of another user, but I haven't figured out if this is possible yet.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking workspace object access control is a good option. Can anyone tell me if admin users automatically have access to all objects in a workspace? Is there anything I may have missed that would compromise this solution? Are any of my assumptions incorrect? Are there viable alternatives I'm missing?&lt;/P&gt;</description>
    <pubDate>Tue, 12 Apr 2022 16:13:56 GMT</pubDate>
    <dc:creator>dvmentalmadess</dc:creator>
    <dc:date>2022-04-12T16:13:56Z</dc:date>
    <item>
      <title>Store a secret only accessible to the current user</title>
      <link>https://community.databricks.com/t5/machine-learning/store-a-secret-only-accessible-to-the-current-user/m-p/23056#M1301</link>
      <description>&lt;P&gt;During an interactive notebook session, I want a user to be able to retrieve a secret specific to that user. I haven't decided on storage mechanisms, but I'm open to storage mechanisms that can scalably authorize access to a single user and that I can write the secret from an external service. I have looked into the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/secret-acl.html" alt="https://docs.databricks.com/security/access-control/secret-acl.html" target="_blank"&gt;Databricks Secrets&lt;/A&gt;: with a limit of 100 scopes, this does not scale beyond 100 users and I work in an engineering organization with over 200 people&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/credential-passthrough/index.html" alt="https://docs.databricks.com/security/credential-passthrough/index.html" target="_blank"&gt;IAM credential passthrough&lt;/A&gt;: does not support MLFlow (my data science team uses MLFlow), and according to my reading it does not support non-admin users calling Scala (I have at least one team that requires the use of Scala)&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/table-acls/index.html" alt="https://docs.databricks.com/security/access-control/table-acls/index.html" target="_blank"&gt;Table Access Control&lt;/A&gt;: I could use this to create a view that is limited to results matching CURRENT_USER, but won't work for users who need to use Scala&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.databricks.com/security/access-control/workspace-acl.html" alt="https://docs.databricks.com/security/access-control/workspace-acl.html" target="_blank"&gt;Workspace object access control&lt;/A&gt;: it has an API I can use to write secrets, and I can limit access by user. I would prefer if I can prevent admins from reading the secret of another user, but I haven't figured out if this is possible yet.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking workspace object access control is a good option. Can anyone tell me if admin users automatically have access to all objects in a workspace? Is there anything I may have missed that would compromise this solution? Are any of my assumptions incorrect? Are there viable alternatives I'm missing?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 16:13:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/store-a-secret-only-accessible-to-the-current-user/m-p/23056#M1301</guid>
      <dc:creator>dvmentalmadess</dc:creator>
      <dc:date>2022-04-12T16:13:56Z</dc:date>
    </item>
    <item>
      <title>Re: Store a secret only accessible to the current user</title>
      <link>https://community.databricks.com/t5/machine-learning/store-a-secret-only-accessible-to-the-current-user/m-p/23059#M1304</link>
      <description>&lt;P&gt;I ended up using Databricks Secrets as the storage mechanism after learning from my account rep that the limit is soft and we can request a higher scope limit. In this case, each user gets a dedicated scope and no other users have access.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:29:47 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/store-a-secret-only-accessible-to-the-current-user/m-p/23059#M1304</guid>
      <dc:creator>dvmentalmadess</dc:creator>
      <dc:date>2022-08-05T18:29:47Z</dc:date>
    </item>
  </channel>
</rss>

