-
New Feature
-
Resolution: Unresolved
-
Major
-
None
We are using an Active Directory as security realm / for the Jenkins login which does not differ between a Firstname.Lastname and a firstname.lastname. Both notations can be used for the login.
The folder-auth-plugin however differs in the notation. Granting permission for the SID firstname.lastname will not grant the permission if the user logs in with a differnt notation (Firstname.lastname / Firstname.Lastname / ...).
This behaviour shall be removed so that a user logging in with Firstname.Lastname is matched with the SID firstname.lastname.
Hi. This is a known issue not just in this plugin but also in role-strategy plugin. You may also want to take a look at
JENKINS-34545We can check whether the usernames are case sensitive or not at runtime using https://javadoc.jenkins.io/hudson/security/SecurityRealm.html#getUserIdStrategy-- but this may lead to significantly reduced performance.
It is possible to have a correct and efficient implementation but it might require some changes to Jenkins core. Feel free to create a pull request if you can think of a better solution than https://github.com/jenkinsci/role-strategy-plugin/pull/43.