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 had
the same prob.
On Friday, October 9, 2015 at 2:22:19 AM UTC-5, Sverre Moe wrote:
>
> 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.company.com
> Manager password: ldapUserPassword
> Display Name LDAP Attribute: displayName
> Email Address LDAP Attribute: mail
>
> There is an port opening between my Jenkins server and helios.company.com
> since ldapsearch is working fine
> ldapsearch -D ldapu...@arctic.company.com -w ldapUserPassword -h helios.
> company.com -b "dc=arctic,dc=company,dc=com" "samaccountname=user"
>
>
> What is missing from the configuration?
>
> If I use the same configuration on another Jenkins running within the same
> subnet of my ldap server, it works. I then cannot falter the configuration,
> however why does ldapsearch work?
>
> I cannot see anything wrong in the Jenkins log (it is empty). I have added
> logger for org.acegisecurity, hudson.security and jenkins.security with log
> level INFO.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/09dba699-90e4-48c8-8ea9-4e3a8d955a59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
