Status: Resolved (View Workflow)
Version 1.579 on Ubuntu 12.04.5 LTS
With LDAP auth, the sAMAccountName containing uppercase case letters does not work with Global Security. For example, user ID "testuser" can be specified in the Global Security as expected. However, user ID "TEstuser" does not work as expected with the Global Security specified as TEstuser. In the Jenkis home dir there is a dir for either users/testuser/config.xml and users/TEstuser/config.xml. It just doesn't work with the ID containing uppercase letters.
- is related to
JENKINS-22247 Provide an extension point to define user id case sensitivity contract
Since the core issue appears to be fixed, are there any plans to update this plugin to make use of the new API?
Have you tried setting the case sensitivity?
The above shows when you click the Advanced button... then clicking on the Case sensitivity button you get
Where you can control exactly the case sensitivity settings of the group names field you are resolving as well as the user name field you are resolving.
LDAP plugin has supported case sensitivity since 2104712d8c2bbce060a218f7a997ada49ebced28 (i.e. Aug 2014)
We are awaiting a LTS release that has the https://github.com/jenkinsci/jenkins/commit/554e087a0a64007fa4a251d1de1d32e5eaeb812e change in it before we push the ldap plugin changes that allow selecting the case sensitivity strategy for the field that you use as username