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
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
My actual set-up is:
JIRA and confluence connect to crowd for user-authentication, crown is connected to my company's active directory (read only). For external team members i use the internal crowd database.
Now i have to add every groups twice in AD and internal db in crowd with exact same name (for example "jira-developers"). So they appear in JIRA and confluence as if they belong to the same group.
Question: Is this best practice in case of read only AD?
The other alternative is to configure Crowd to use a delegated authentication directory to connect to AD, but bear in mind that users won't automatically be updated in such a configuration. (There are some options which allow the users to be created and updated on login which you can turn on, but the user does still need to log in.)