Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Crowd should not be case-sensitive for ldap request

Our ldap contains data that are not case sensitive (see uniquemember.jpg), since ldaps are not case sensitive, all our ldap request work fine.

The directory configuration in crowd is case sensitive (see crowd-Directory-conf.jpg), we don't obtain the same result if we use lower case or upper case.

It uses to work fine en crowd 1.6.

It affects crowd versions : 2.2, 2.3, 2.4

1 answer

0 votes
JustinK Rising Star Apr 03, 2012

Hi Aurélien,

The answer is in the error message. Your directory configuration has Roles configured, and it is pointing to the same DN as another entity (Users or Groups). Crowd cannot perform in this manner, so I would suggest that you disable Roles, especially if:

1. You are not using them

2. Crowd is trying to deprecate these and they will be dropped in a future release.

Please note, that is is not a case-sensitivity issue, Crowd is case-insensitive, Crowd was actually a lot more case-sensititve in versions before 2.0!



Hi Justin,

The group membership issue that Aurélien is facing has nothing to do with roles. It is actually a known bug by Atlassian that will be fixed in Crowd 2.4.1.

Looks like some part of Crowd are still case sensitive ;-)



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events