|
||||||||
|
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.
This is also causing problems when working across different domains.
All of my users have their credentials in "MyDomain.mycompany.com". However the Jenkins server is hosted in "MyDEVDomain.mycompany.com". With out being able to speicify the BindDN (MyDomain\UserID), it attempts to authenticate against the default AD server in which the server is hosted.
As in the pictures above, I've tested this out by patching the active directory plugin to show Bind DN and Bind Password, regardless of windows or *nix OS. And this works for me.