cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Unexpected behaviour when creating multiple Account-Level Accounts

Danny_Heinrich
New Contributor

We've had a qustion regarding possibly unexpected behaviour when creating multiple accounts on the account-level on https://accounts.cloud.databricks.com/.

Short Version:

It's possible to create multiple accounts with different letter-cases on https://accounts.cloud.databricks.com/. 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.

Is this working as intended ?

Long Version:

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".

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.

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).

For deploying Terraform we would first need to login on the account-level, i.e., https://accounts.cloud.databricks.com/. 

To solve this issue we created a second account on the account level with "John.Doe@example.com". 

Interestingly this actually worked and there were now two different Users with the same Email.

However, when resetting the password for one user we would also change it to the same password for the other user. 

Steps to reproduce: 

Create two Accounts with the same E-Mail address, but different letter casing on https://accounts.cloud.databricks.com/

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.

Expected behaviour:

  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.

0 REPLIES 0
Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.