On 03/01/13 10:51, Levin, Ilya wrote:
I’m trying to use ldap in my Jenkins (v 1.485).
I configured the ldap connection under the security relam, and it seems
that the connection with the ldap server was established.
I did a little test and entered 2 users, a false one and an existing
one. As you can see Jenkins identified this – which tells me that the
connection exist.
HOWEVER when I try to log in as the legitimate user, Jenkins “thinks”
for about 5 min and then do nothing – doesn’t login.
Moreover Jenkins doesn’t log anything as if nothing happened – without
the log I cannot understand what went wrong.
I had to debug a weird LDAP login problem once, but either I didn't use
the Jenkins logs, or didn't get far.
I ended up using tcpdump to see what was happening (since our LDAP
server at the time wasn't secured).
Maybe you can do something similar to see whether Jenkins is correctly
doing the DNS lookup and TCP connection to the LDAP server, and why/what
is timing out.
Chris
