kiranchavala commented on issue #8523:
URL: https://github.com/apache/cloudstack/issues/8523#issuecomment-4420045898

   > > accounts don't have email addresses, users do. That makes our design and 
bit awkward for integration with oauth, as users log into an account to do 
things on the accounts behalf. I think we should allow users with the same 
email in different accounts, but what can not happen is the same user-id in a 
domain. I think the bug is not allowing creation of multiple users in different 
accounts with the same email, but not allowing the login of said users. cc 
[@harikrishna-patnala](https://github.com/harikrishna-patnala)
   > 
   > [@DaanHoogland](https://github.com/DaanHoogland) we cannot allow oauth 
login if multiple users are found with same email id. The question raises to 
which user to create the login.
   > 
   > I kind of agree with [@kiranchavala](https://github.com/kiranchavala) to 
somehow give operators to configure such that duplicate emails are not allowed. 
I could think of the following solutions.
   > 
   >     1. Create a new domain level setting or or new detail while creating 
the domain, which describes whether same emails are allowed or not. By default 
we can keep the old way
   > 
   >     2. Another solution is while enabling oauth on specific domain, check 
if there are any existing users having duplicate emails and throw the exception 
and also while creating new users check if oauth is enabled and if there is 
same email present in the database or not
   > 
   > 
   > cc [@kiranchavala](https://github.com/kiranchavala)
   
   Thanks @harikrishna-patnala, I like the first option 1
   
   to have a setting at Domain/zone/Global level,  which prohibits the account 
creation if there is an already account with the same email address 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to