Re: LDAP in Jenkins Fails, but ldapsearch works

2016-04-20 Thread Shravan naidu
The Jenkins LDAP plugin has a bug which fills up manager DN field with a random string and that fails the login procedure. Luckily, the manager DN field is not mandatoy to be filled and can be left blank. I would recommend to fill root DN and leave rest of the field blank and try logging in. I

Re: LDAP in Jenkins Fails, but ldapsearch works

2015-10-15 Thread Adis Azizan
Same issues with me. Anybody actually can solve this? I try to use ldaps:// and it given me different error which is SSL Exception On Friday, 9 October 2015 15:22:19 UTC+8, Sverre Moe wrote: > > I have configured authentication with LDAP > > My LDAP Configuration: > Server: helios.company.com > r

Re: LDAP in Jenkins Fails, but ldapsearch works

2015-10-13 Thread James Nord
if you are using port 389 then unless TLS upgrade is happening then this is all plaintext (including your passwords!) so I would suggest a network capture with wireshark and then compare Jenkins and ldapsearch and see if you can spot some differences that can lead you to understand why this is

Re: LDAP in Jenkins Fails, but ldapsearch works

2015-10-12 Thread Sverre Moe
I spoke to soon. It worked for a short while, but now I am getting several invalid login "Invalid login information. Please try again. " There is still nothing in the log. What is Jenkins doing different than ldapsearch. It should communicate with the server on default port 389. I am using a Pro

Re: LDAP in Jenkins Fails, but ldapsearch works

2015-10-09 Thread Sverre Moe
I have done nothing with the LDAP configuration, but now it works. It takes 30 seconds before I'm logged in. The only thing I have done is to add Proxy configuration to Jenkins. I have tried both samaccountname and sAMAccountName. I don't think ours is case sensitive. Using DOMAIN\username does

Re: LDAP in Jenkins Fails, but ldapsearch works

2015-10-09 Thread Maciej Jaros
Sverre Moe (2015-10-09 09:22): |Usersearch base:ou=users | I think it should be "CN=Users". | Usersearch filter:samaccountname={0} | Not sure if case matters, but we use "sAMAccountName={0}" |ManagerDN:ldapu...@arctic.company.com | This is Windows AD? If so then I think you should use "do

LDAP in Jenkins Fails, but ldapsearch works

2015-10-09 Thread Sverre Moe
I have configured authentication with LDAP My LDAP Configuration: Server: helios.company.com root DN: dc=arctic,dc=company,dc=com User search base: ou=users User search filter: samaccountname={0} Group membership: Parse user attribute for list of groups => memberOf Manager DN: ldapu...@arctic.comp