Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,458,125
Community Members
 
Community Events
176
Community Groups

How to combine a read only AD with extra users not stored in AD

Jan Dähler
Jan Dähler Feb 19, 2015

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?

Answer
Watch
Like Be the first to like this
430 views

1 answer

0 votes
Caspar Krieger
Caspar Krieger Atlassian Team Feb 21, 2015

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.)

Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS

Atlassian Community Events

See all events