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.
I want to configure "Delegated Authentication Directory" to be able to have real-time changes in Active Directory reflected on Authentication. In other words, once a user chagnes his/her password, I do not want to need to synchronize Crowd Directory, and Crowd delegates authentiction to Active Directory, but the problem that I faced is that I when I use the same settings that I used for Connector Directory causes problem with this type of Crowd Directory. Event though I can search successfully, I can not update the settings and I got error message.
The other problems is that the configuration screen does not look like snapshot in the documentation of this type of directory configuration.
Hi Grant,
I could only find this documentation for setting a delegated LDAP directory on crowd. Actually using the exact same setting for a delegated and a connector directory may be possible, but I believe it won't be good to use both directories for the same application in crowd.
If you want to use the delegated user directory, I would recommend to remove the connector directory from the same application window and set just the delegated user directory for that specific application.
Cheers,
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.