Quantcast

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

JIRA noreply@jenkins-ci.org
Keith Starling created JENKINS-13674:
----------------------------------------

             Summary: AD Auth with Matrix authentication now requires LDAP name rather than username
                 Key: JENKINS-13674
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
             Project: Jenkins
          Issue Type: Bug
          Components: active-directory
    Affects Versions: current
            Reporter: Keith Starling


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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162401#comment-162401 ]

algoRhythm99 commented on JENKINS-13674:
----------------------------------------

Usernames in the authentication matrix DO work.
However it is case-sensitive and must match the user's sAMAccountName casing in AD.

               

> AD Auth with Matrix authentication now requires LDAP name rather than username
> ------------------------------------------------------------------------------
>
>                 Key: JENKINS-13674
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
>             Project: Jenkins
>          Issue Type: Bug
>          Components: active-directory
>    Affects Versions: current
>            Reporter: Keith Starling
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162446#comment-162446 ]

Andreas Zoufal commented on JENKINS-13674:
------------------------------------------

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.
               

> AD Auth with Matrix authentication now requires LDAP name rather than username
> ------------------------------------------------------------------------------
>
>                 Key: JENKINS-13674
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
>             Project: Jenkins
>          Issue Type: Bug
>          Components: active-directory
>    Affects Versions: current
>            Reporter: Keith Starling
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162451#comment-162451 ]

John Salvo commented on JENKINS-13674:
--------------------------------------

This is a duplicate of:

https://issues.jenkins-ci.org/browse/JENKINS-13650

               

> AD Auth with Matrix authentication now requires LDAP name rather than username
> ------------------------------------------------------------------------------
>
>                 Key: JENKINS-13674
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
>             Project: Jenkins
>          Issue Type: Bug
>          Components: active-directory
>    Affects Versions: current
>            Reporter: Keith Starling
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kohsuke Kawaguchi resolved JENKINS-13674.
-----------------------------------------

    Resolution: Duplicate
   

> AD Auth with Matrix authentication now requires LDAP name rather than username
> ------------------------------------------------------------------------------
>
>                 Key: JENKINS-13674
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
>             Project: Jenkins
>          Issue Type: Bug
>          Components: active-directory
>    Affects Versions: current
>            Reporter: Keith Starling
>
> 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).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Loading...