ADAM is an LDAP directory service.

      The way Jenkins does authentication in LDAP is

      1. bind as the administrator DN and search for the User.
      2. bind as the user DN found in step 1
      3. Get the users DN details

      The LDAP authentication process implemented by Jenkins, is not compatible with every Active Directory configuration in which Jenkins Users have not “Readers” role.

          [JENKINS-29382] LDAP authentication doesn't work with ADAM

          Björn Martin added a comment -

          Kind of duplicated by JENKINS-37480 which reports this as a bug. I have the same issue with an OpenLDAP installation by our OPS team that does not allow READ for users. If either is resolved the other can (most probably) get closed as well.

          Björn Martin added a comment - Kind of duplicated by JENKINS-37480 which reports this as a bug. I have the same issue with an OpenLDAP installation by our OPS team that does not allow READ for users. If either is resolved the other can (most probably) get closed as well.

          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
            fbelzunc Félix Belzunce Arcos
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: