-
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.
[JENKINS-67943] Do not differ between upper / lower case in SID
Christoph
created issue -
Ian Williams
made changes -
| Environment |
Original:
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 loggin in with Firstname.Lastname is matched with the SID firstname.lastname. |
Ian Williams
made changes -
| Description |
New:
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. |