Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Duplicate
-
Component/s: active-directory-plugin
-
Labels:None
-
Similar Issues:
Description
As of active-directory 1.27, the system resolves the full LDAP name for the user, and apparently attempts to use this rather than the username for comparison in matrix based authentication. This is a pain, since it's much easier and more consistent to use usernames for rights management (plus that's how it used to work).
Attachments
Activity
Keith Starling
created issue -
I'm sorry but I cannot get it to work. After updating to 1.27 I can login with my usual username, but I don't have the right to manage jenkins, I'm just a viewer now. There is something what has changed.
I had to restore the old version manually (I hope I did everything right), in ${JENKINS_HOME}/plugins I had to copy active-directory.bak over active-directory.jpi. Now I works again with the old version.
Andreas Zoufal
added a comment - I'm sorry but I cannot get it to work. After updating to 1.27 I can login with my usual username, but I don't have the right to manage jenkins, I'm just a viewer now. There is something what has changed.
I had to restore the old version manually (I hope I did everything right), in ${JENKINS_HOME}/plugins I had to copy active-directory.bak over active-directory.jpi. Now I works again with the old version. This is a duplicate of:
John Salvo
added a comment - This is a duplicate of:
https://issues.jenkins-ci.org/browse/JENKINS-13650 | Field | Original Value | New Value |
|---|---|---|
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Workflow | JNJira [ 144141 ] | JNJira + In-Review [ 190928 ] |
Usernames in the authentication matrix DO work.
However it is case-sensitive and must match the user's sAMAccountName casing in AD.