Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,467,419
Community Members
 
Community Events
177
Community Groups

Crowd with ApacheDS - too many users

Last night, I moved my Crowd authentication from a server with OpenLDAP/Posix to a different server with ApacheDS. Both LDAP servers have 76 LDAP users, but I didn't intend to allow them all to log into the Atlassian suite. This morning, I found that I was locked out of Crowd because our license only allows for 50 users, and any actions within Crowd redirect me to a license page.

Is there a way to tell Crowd that I don't want to actually allow all 76 users to log in? My staging environment auths against the OpenLDAP setup still, with a 50 person license, and I haven't run into this problem.

1 answer

0 votes

In that case, you'll need to create filters so just some users will be imported.

Hope it helps!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events