• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ldap-plugin
    • None

      I am trying to integrate my corporate LDAP with jenkins. I tried different combinations of the LDAP parameters, the authentication would simply not work. It does not throw any error. I do not see anything in the logs either. Is there a way to troubleshoot LDAP related issues. Is there anywhere else I could look to see what error it is actually throwing? Also is there a way I could test the LDAP authentication on the jenkins page directly something like a test connection.

          [JENKINS-36374] troubleshooting ldap authentication failure

          Harry Johnson added a comment -

          I've having similar issues - I'm able to create the LDAP setup, which does connect to the LDAP server successfully, but I can't actually log in with any proper ID. I'm already using similar setups with our JIRA, Confluence, Anthill, SVN setups, which work just fine.
          Have you been able to fix your issue?

          Harry Johnson added a comment - I've having similar issues - I'm able to create the LDAP setup, which does connect to the LDAP server successfully, but I can't actually log in with any proper ID. I'm already using similar setups with our JIRA, Confluence, Anthill, SVN setups, which work just fine. Have you been able to fix your issue?

          qi song added a comment -

          Create/Update a dedicated Logs recorder (LDAP) as explained in Jenkins Logging including the following list:

          hudson.security = ALL
          jenkins.security = ALL
          org.acegisecurity.ldap = ALL
          org.acegisecurity.providers.ldap = ALL
          Having done that, first test your AD settings and then try to log in with a LDAP user (“UserX”).

          reference https://support.cloudbees.com/hc/en-us/articles/204983360-How-to-diagnose-LDAP-integration-problems

          qi song added a comment - Create/Update a dedicated Logs recorder (LDAP) as explained in Jenkins Logging including the following list: hudson.security = ALL jenkins.security = ALL org.acegisecurity.ldap = ALL org.acegisecurity.providers.ldap = ALL Having done that, first test your AD settings and then try to log in with a LDAP user (“UserX”). reference https://support.cloudbees.com/hc/en-us/articles/204983360-How-to-diagnose-LDAP-integration-problems

          Björn Martin added a comment -

          Not sure if this item still needs resolving since it was posted 9 months ago with zero response from the reporter. But I have similar issues. Mine look like JENKINS-37480 (users not having READ permission) so I will hop over to that one. Just a hint in case this item stays idle.

          Björn Martin added a comment - Not sure if this item still needs resolving since it was posted 9 months ago with zero response from the reporter. But I have similar issues. Mine look like JENKINS-37480 (users not having READ permission) so I will hop over to that one. Just a hint in case this item stays idle.

          Oleg Nenashev added a comment -

          In order to set proper expectation, I have unassigned Kohsuke from this tickets.
          Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

          Oleg Nenashev added a comment - In order to set proper expectation, I have unassigned Kohsuke from this tickets. Currently there is no Default assignee in the LDAP plugin, any contributions will be appreciated.

            Unassigned Unassigned
            npep07 Sajala Rajendran
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: