|
||||||||
|
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 causing an issue for me attempting to stand up a Jenkins instance on Windows 7. If the Jenkins service is running as a local user, even if the machine is joined to a domain, it appears that the Active Directory plugin fails to look up the AD information. I believe we need the ability to specify the bindName, bindPassword, and groupLookupStrategy under the Advanced button, even when running Jenkins on Windows.
Running the service as a domain user has no issues.