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

Your Points Tracker
  • 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
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?
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

Can Crowd try the next directory after failed authentication?

This isn't so much about a failover directory, but rather if the same user exists in two directories, and the account happens to be disabled/locked in the first directory.  Normally crowd gets the rejection from the first directory and doesn't try to authenticate the user against the next directory.  Is there a way to configure it such that Crowd will attempt to authenticate the username/password against all configured directories?

In my case, I have two delegated authentication directories against two trusted domains.  Users have gone back and forth between the two domains over the years, and IT doesn't have much of an appetite to do some housecleaning.

1 answer

0 votes
Bruno Vincent Community Leader Mar 17, 2019


As per Atlassian's documentation

If the user belongs to more than one directory, Crowd uses the first directory in which the user appears, as determined by the directory order.

What you get is thus Crowd's standard behaviour. I'm afraid there is no way to change it by configuration.

What about handling it on the application side? Could I add a second application entry with the directory order reversed, then add a second crowd server to the application under the new application name?

ie, can Jira be configured to fail to the next directory if authentication fails?

Bruno Vincent Community Leader Mar 18, 2019

I'm afraid this won't work. As per Jira documentation:

The directory order is significant during the authentication of the user, in cases where the same user exists in multiple directories. When a user attempts to log in, the application will search the directories in the order specified, and will use the credentials (password) of the first occurrence of the user to validate the login attempt.

Suggest an answer

Log in or Sign up to answer
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