[jira] [Commented] (CLOUDSTACK-7073) Account/User creation: able to create user with the same name in the same domain in Clustered MS setup

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054292#comment-14054292 ] 

ASF subversion and git services commented on CLOUDSTACK-7073:
-------------------------------------------------------------

Commit 5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a in cloudstack's branch refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5a96d8e ]

CLOUDSTACK-7073: Added domainId field to the user table in order to restrict duplicated users creation on the db level


> Account/User creation: able to create user with the same name in the same domain in Clustered MS setup
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7073
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7073
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.5.0
>
>
> In the Java code we prohibit user to have duplicated names inside the same domain. But in the DB the constraint is missing in cloud.account/cloud.user table, so it is still possible to violate the rule by initiating the create call from parallel threads issued either by the same MS, or by multiple MS in the clustered MS setup.
> To fix, have to introduce some kind of the global lock, or db constraint preventing multiple threads to insert the record with the same username.



--
This message was sent by Atlassian JIRA
(v6.2#6252)