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
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||JNJira [ 131875 ]||JNJira + In-Review [ 200996 ]|
|Component/s||_unsorted [ 19622 ]|
|Component/s||security [ 15508 ]|