We use active directory plugin for allowing users to login to Jenkins ( run on a CentOS box )
The issue we had was that once whilst trying to make some change in ‘Configure Global Security’ and after saving it , no user was able to login using their AD credentials . This happened because Chromes autofill , added the username as the ‘bindName’ in the Advanced fields for ‘Active Directory’ . This was very disruptive and serious , but happened very silently as normally the ‘Advanced fields’ are not expanded and seen for this to be noticed . The fix of this was to manually remove the <bindName> entry from the config.xml and restart the Jenkins instance . This email is as FYI and in case others have seen this too . Will probably file an issue in Jenkins for this . Taher . ________________________________ This email and any attachments may contain confidential and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments) by others is prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete this email and any attachments. No employee or agent of TiVo Inc. is authorized to conclude any binding agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo Inc. may only be made by a signed written agreement. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/712CB46A62E6AA4EA165C01FEC43CD7A085AC065%40SJEXMB02.Tivo.com. For more options, visit https://groups.google.com/d/optout.
