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

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!



Bruno Vincent Community Champion Apr 03, 2012

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
Community showcase
Published Friday in Jira Service Desk

Are you a Jira Service Desk agent? We want to talk to you!

Are you a whiz at handling tickets and looking at how you can further optimize your workflow with automation? Do you tackle detailed customer support questions while simultaneously getting flooded wi...

138 views 0 7
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you