You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.