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.)
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot