Status: Resolved (View Workflow)
Platform: PC, OS: Windows 2000
Hudson HudsoLDAP authentification is case sensitive. LDAP doesn't do case
comparaison during login verification on LDAP side. But Hudson does. I enter
following user in my project matrix table:
"Arnold Pipo" (with all access: Administrator)
When I try to connect with following id: "arnold pipo", I can connect but with
only anonymous rights. If I cannot with "Arnold Pipo", I have the correct rights
that I defined in my matrix. It seems that authentification is ok on LDAP side,
but Hudson seems to compare "Arnold Pipo" and "arnold pipo" but it doesn't match
(Case problem). So it considers him as anonymous user.
- is duplicated by
JENKINS-9771 LDAP group search is not case sensitive, but ACL determination is case sensitive
- is related to
JENKINS-17674 Expand SecurityRealm to support case insensitivity better
JENKINS-22247 Provide an extension point to define user id case sensitivity contract
...which is written up vs. Active Directory.
Please fix, there so many different requests!
I just had a problem with the same root cause: Jenkins didn't find my groups because I accidentally had one uppercase letter in my username during login.
I think the login should either fail with wrong casing or Jenkins should just update the username from LDAP, so it continues with the correct username instead of the one with bad casing form the login.
This issue is someway related to