|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
After analyzing my LDAP hierarchy, I devised the correct manager DN in the format described in your link:
CN=My Full Name,OU=Workers,DC=abc,DC=corp,DC=company,DC=com
However, that did not change the behavior at all.
The plugin prints no errors on the configuration, thus implying that the configuration is correct and that it can successfully login to the LDAP server. The Groovy script I posted above also confirms that: it can validate user names successfully.
But when I try to login to Jenkins, I see the following behavior:
In summary: the username is identified to be correct, the password is also correct (as it is the manager password), but login is still impossible.