Hi Everyone,
We are in an ambiguous situation that we have 100+ duplicate users coming from two different AD's from Crowd, those duplicate users usernames be like ex: twhite (AD 1 **old**) and twhite3 (AD 2 **new**) and we thought of converting all records like assignee, reporter etc from twhite to twhite3 manually or jira-python script, after converting records user would not see his old username i.e. twhite while start typing name in user picker field
I was trying to disable/inactive user from crowd side but could not able to do that showing an error
Note1: Removing or disabling the user from AD 1 **old** LDAP side will affect the user to use other applications and removing AD 1 **old** from the crowd is not possible at this moment because of management call.
Note2: Those who have unique ID between both AD's not an issue. like tnaik (AD 1 **old**) and tnaik (AD 2 **new**)
Any suggestions would be much helpful.
Regards
T
@Teja the AD2 has the priority ? Usually i set the principal ad and sync they, generally this works for me in the past.
Sorry for the delayed response due to the weekend,
Yes, the AD2 has the priority and we are going to make AD2 as primary in Crowd.
sync works when users have same username between both AD's like I said
tnaik (AD1)
tnaik (AD2)
when the user has a different username b/w both AD's never sync
twhite (AD1)
twhite3 (AD2)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carlos Faddul Any suggestions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Teja I will owe you this
I don't have any VM to test and remember how it could help you =\
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems to work when we remove the user from jira-users from (AD 1 **old**) from crowd side.
I can see a reduced user license count when we do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, that did not work, by using the above we can refrain users to not log in to the system.
Still we can see both user drop down.
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.
@Teja no luck =\
Maybe atlassian support for crowd, i don't have VM's of server anymore since february =(
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.