Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,069
Community Members
 
Community Events
168
Community Groups

Understanding Crowd Alias settings in JIRA

I am trying to integrate a longstanding JIRA installation with Crowd and our corporate AD. I can login to jira using my corporate login via Crowd and my "old" JIRA login.

I setup aliasing in Crowd and understand that I still have to use my old username (right?), but I expected to use my AD password?

Could someone explain exactly how this should work. Do I use my old JIRA username when logging into JIRA with my AD password ?

(I still have the JIRA authenticator enabled but second in the hiearchy).

Thanks,

Dylan

1 answer

1 accepted

0 votes
Answer accepted
EddieW Rising Star Sep 18, 2011

Hmm, that's not quite my take on the recommended use of aliasing. I beleive aliasing is more intended for cases where several apps are using crowd but all have slightly different IDs (i,e. confluence vs jira). In your case you are migrating the entire user population from internal management to extenrla management.

  1. Ignoring your "old" id, get jira configured to use crowd as a directory within Jira, and authenticating using both the new username and new passowrd (both from AD)
  2. Deactivate all the non-AD accounts (not removeing them!) http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+JIRA#IntegratingCrowdwithAtlassianJIRA-KnownLimitations
  3. Use the JQL to have users migrate any previously owned or created tickets to their new username via the batch updater.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events