<?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 Unexpected behaviour when creating multiple Account-Level Accounts in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unexpected-behaviour-when-creating-multiple-account-level/m-p/14315#M8830</link>
    <description>&lt;P&gt;We've had a qustion regarding possibly unexpected behaviour when creating multiple accounts on the account-level on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Short Version:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;It's possible to create multiple accounts with different letter-cases on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;. However all accounts with the same e-mail address seem to share the same password or are assigned the same password when a password reset is performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this working as intended ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Long Version:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;While setting up SSO-Workspace-Access for our Users we did encounter a small issue with Azure Active Directory (AAD). Initially our Users were manually created with lower-case emails like "john.doe@example.com".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However when creating Users via AAD, they had to be created using Camel-Case lettering e.g. "John.Doe@example.com", which meant removing the original Users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When deploying our infrastructure via terraform we then encountered an issue with authenticating to the workspace since there were now two different users on account-level (john.doe) and workspace-level (John.Doe).&lt;/P&gt;&lt;P&gt;For deploying Terraform we would first need to login on the account-level, i.e., &lt;A href="https://accounts.cloud.databricks.com/.&amp;nbsp;" target="test_blank"&gt;https://accounts.cloud.databricks.com/.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;To solve this issue we created a second account on the account level with "John.Doe@example.com".&amp;nbsp;&lt;/P&gt;&lt;P&gt;Interestingly this actually worked and there were now two different Users with the same Email.&lt;/P&gt;&lt;P&gt;However, when resetting the password for one user we would also change it to the same password for the other user.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Steps to reproduce:&amp;nbsp;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create two Accounts with the same E-Mail address, but different letter casing on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Change the password of one account, the other account should now have the same password and be able to login using the password that was just set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Expected behaviour:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Disallow creation of another user if one with the same email already exists or allow creation of multiple accounts with the same email, but they should not share passwords.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Jul 2022 05:56:11 GMT</pubDate>
    <dc:creator>Danny_Heinrich</dc:creator>
    <dc:date>2022-07-08T05:56:11Z</dc:date>
    <item>
      <title>Unexpected behaviour when creating multiple Account-Level Accounts</title>
      <link>https://community.databricks.com/t5/data-engineering/unexpected-behaviour-when-creating-multiple-account-level/m-p/14315#M8830</link>
      <description>&lt;P&gt;We've had a qustion regarding possibly unexpected behaviour when creating multiple accounts on the account-level on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Short Version:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;It's possible to create multiple accounts with different letter-cases on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;. However all accounts with the same e-mail address seem to share the same password or are assigned the same password when a password reset is performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this working as intended ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Long Version:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;While setting up SSO-Workspace-Access for our Users we did encounter a small issue with Azure Active Directory (AAD). Initially our Users were manually created with lower-case emails like "john.doe@example.com".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However when creating Users via AAD, they had to be created using Camel-Case lettering e.g. "John.Doe@example.com", which meant removing the original Users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When deploying our infrastructure via terraform we then encountered an issue with authenticating to the workspace since there were now two different users on account-level (john.doe) and workspace-level (John.Doe).&lt;/P&gt;&lt;P&gt;For deploying Terraform we would first need to login on the account-level, i.e., &lt;A href="https://accounts.cloud.databricks.com/.&amp;nbsp;" target="test_blank"&gt;https://accounts.cloud.databricks.com/.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;To solve this issue we created a second account on the account level with "John.Doe@example.com".&amp;nbsp;&lt;/P&gt;&lt;P&gt;Interestingly this actually worked and there were now two different Users with the same Email.&lt;/P&gt;&lt;P&gt;However, when resetting the password for one user we would also change it to the same password for the other user.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Steps to reproduce:&amp;nbsp;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create two Accounts with the same E-Mail address, but different letter casing on &lt;A href="https://accounts.cloud.databricks.com/" target="test_blank"&gt;https://accounts.cloud.databricks.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Change the password of one account, the other account should now have the same password and be able to login using the password that was just set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Expected behaviour:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;Disallow creation of another user if one with the same email already exists or allow creation of multiple accounts with the same email, but they should not share passwords.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2022 05:56:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unexpected-behaviour-when-creating-multiple-account-level/m-p/14315#M8830</guid>
      <dc:creator>Danny_Heinrich</dc:creator>
      <dc:date>2022-07-08T05:56:11Z</dc:date>
    </item>
  </channel>
</rss>

