[JIRA] (JENKINS-12619) "Failed to test the validity of the user name" on all security matrices since upgrade

[chris_willia...@dell.com (JIRA)]

Chris Williams commented on JENKINS-12619 "Failed to test the validity of the user name" on all security matrices since upgrade I can reproduce this on Win2k8R2 but it works on RHEL5: Jenkins 1.480.2, Jenkins AD plugin 1.30 On RHEL5, I can see the fields "Site", "Bind DN", "Bind Password", and the button "Test" on the Jenkins Config page. Using Project-based Matrix Auth, both individual users and groups are validated properly. The master config.xml file contains tags for both <bindName> and <bindPassword>. On Win2k8R2, Jenkins running as a Windows service using a domain account, I do not see the Site/Bind DN/Bind Password fields nor the Test button. I only get "Domain Name" and "Domain controller". Using either Matrix auth, both individual and groups fail to validate and throw the org.acegisecurity.BadCredentialsException error listed above. The master config.xml file contains only a <bindPassword> tag, presumably the value of the encrypted password is the password from the domain account used for the Windows service. If I manually add a <bindName> entry to config.xml and reload, Jenkins fails to start and throws the same BadCred exception.

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