|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Ok, I found another workaround. The issue is that the referral points to an invalid server. To fix this, all you have to do is edit your HOSTS file to point the DNS entry back to the LDAP server. In my situation I have Jenkins on a Windows box and the referral points to EXAMPLE.COM.
Edit C:\Windows\System32\drivers\etc\hosts, add the line:
XX.XX.XX.XX example.com
where XX.XX.XX.XX is the IP address of your LDAP server.
Also, unrelated to this bug, but for completeness your LDAP 'User Search Filter' should probably be "SAMAccountName={0}" if you are using LDAP over Active Directory.