Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to Configure Crowd Aliases

I am currently using Crowd version 2.7. I have imported into the Crowd the user database from JIRA and have now configured JIRA/Confluence/etc to authenticate to the Crowd server. I haven't configured SSO and as yet don't wish to.

I'm now implementing an Active Directory server which I wish to use to hold all the user account information and standardise on username formats. To save having to change all the JIRA usernames to the new format I was planning on using Crowd aliases. However I've hit a slight problem.

Say my user database has the usernames configured a_user, b_user, c_user. My active directory contains the new username for a_user of ad_user. I've configured all the directories and groups within the AD and Crowd and assigned them to the JIRA application. However, when I select the username ad_user and try to create the alias a_user I get an error message back stating the username is already in use. The only way I've found to get around this is to delete the user from the JIRA database then create the alias. However, JIRA documentation recommends not deleting users.

What is the correct way of doing this as all the documentation seem to assume an implementation where the JIRA user database is held within the JIRA application, not within Crowd?

Many thanks for any assistance you can provide and apologies if this has been asked before.

1 answer

Hi Kevin,

Just checking to see if I undertood it correctly. You have imported to Crowd the user database from JIRA and you're able to configure the alias only when deleting the username from JIRA directory into Crowd, is that right?

If so, there's no problem with this approach. For JIRA it doesn't matter from which directory in Crowd the user come from. You can safelly delete the user from the directory where you imported JIRA user base in Crowd and define the alias for the LDAP user.

I hope it helps.

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

300 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you