We are having issues getting the correct and non duplicated User Details where we have the same user name on multiple directories. In a nutshell, we can have user name "asmith" on directory A, and another "asmith" on directory B, which are not the same user. We want to get the user details from the [cwd_user] table, but joining on the [user_name] or [lower_user_name] (both the same) brings back duplicates.
Both directories are active ... it's not that we have migrated from one to the other, as per this post.
Also found this link that shows how to use the [app_user] table for the lookup, but it doesn't solve our problem with multiple directories.
How should we go about getting the correct user details for the [CREATOR] column on the [jiraissue] table, as well as the [AUTHOR] column on the [dbo].[changegroup] table?
Users from both directories can work on a single task. Pretty sure we just need to link the directory_id values (no user_name is duplicated within a single directory), but can't find where to look up these values. Is there no way that instead of having user_names all over the database, it can rather specify the UserId values (even if it is in the text format 'IDxxxx')?
Please help
Hello,
If you have the same username in both directories, then user logins under the user in the first user directory in the list. That is why both users work under the same name in Jira.
You can read more info here:
https://confluence.atlassian.com/adminjiraserver071/managing-multiple-directories-802592355.html
Thanks for the quick reply.
So this solution assigns priority based on the directory, right?
So in our example, everything will show up against user "asmith" which is "Adam Smith"* and nothing against "Andrew Smith"*?
And this also means that when either of these people try to login, it is actually authenticating the same account based on who is first in the order of Directory priority.
And if they do have the same password, it technically means that the second priority account is actually logged in as the first priority (i.e. Andrew will log in as Adam in this example)
*Names have been changed to protect the identity of the affected persons :P
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that is right. And if they have different passwords then the user from the lower priority will get the authentication error. The password of the user will be incorrect.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.