Don't allow the creation of user with same Email id in the same domain

[kiranchavala]

ISSUE TYPE

Enhancement/Improvement Request

COMPONENT NAME

Component: API/ UI

CLOUDSTACK VERSION

Cloudstack version 4.18

SUMMARY

Don't allow the creation of user with same Email id in the same domain

Steps to reproduce the issue

1. Navigate to domain > Accounts > Click on a particular Account > Create say user1 with (test@gmail.com)

2. Navigate to domain >Accounts > Click on a particular Account > Create say user2 with (test@gmail.com)

Screenshot

Expected behaviour

Cloudstack should not allow to create the user with same Email address in the same domain

If a oauth is configured for a user in a cloudstack , email address is used as key to identify.

Cloudstack throws an error saying there is an already multiple user having the same email address in the same domain.

It would be proactive checking if we could block the creation of user with same email address during the user creation

[DaanHoogland]

I think this needs more exploration @kiranchavala as it can be useful to have the same user in multiple accounts in the same domain, for some. In the case of OAuth this may be a problem indeed. at the moment it is not allowed to have the same userid, so maybe it is trivial but for some it may make sense to have "dahnUser" and "dahnAdmin", which makes it a backwards compatibility concern as well.

[kiranchavala]

Thanks @DaanHoogland

Can we consider if ouath is enabled in global setting , we should not allow the creation of accounts with same email address

cc @harikrishna-patnala your opinion on this.

[DaanHoogland]

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