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
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!
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 ;-)
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events