Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-1802

LDAP authentification against AD didn't works

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: _unsorted
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      I do some tests on Hudson 1.221 and the LDAP authentification still didn't works
      against AD since it didn't want anonymous binding and require a binding
      login/pwd for operations

      I used a network sniffer to track down the problems.

      • On the admin page changes to the LDAP manager login are correctly saved on the
        config.xml but are not used when LDAP connection is done on the admin page

      It seems only the password is sent on the wire during the binding operation on
      the admin page.

      At startup time Hudson, using the saved config.xml LDAP parameters, does a
      successfull bind (login and password are sent) to AD.
      But when a user try to authentificate, Hudson didn't use the same 'socket
      connection' (where binding has been done) and sus the request failed.

      Hope it will help

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            henri_gomez henri_gomez
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: