Daniel is on to something regarding matching case. When it comes to case [in]sensitivity, however, the behavior of Jenkins is a bit of a mystery.
When I was using a Linux machine as the Jenkins server, there was no mystery. A mixed case login ID was always treated with case sensitivity. Now that I have been moved to a Windows based server, the rules seem to have changed. My Security Realm is set to "Jenkins' own database" and I allow users to sign up. As an example, I can have a user signup as "JamesYoung". I can then go to the Matrix-based security under Authorization and add the user "JamesYoung" (note the mixed case). I can give "JamesYoung" Overall Adminstrator rights. For a while, "JamesYoung" will have Adminstrator rights and things seem to be going as expected. At some point, however, "JamesYoung" no longer has Administrator rights. When I look at the Users list, I see that "JamesYoung" was added as "jamesyoung", even though the user specified mixed case when he signed up. These are the aspects of Jenkins' behavior that I think are odd: (1) Jenkins down-cases the User ID's of users who sign up. (2) Even though Jenkins has down-cased the ID, the ID can be entered into the Matrix-based security in mixed case. (3) The mixed-case ID that was added to the matrix and granted Administrator rights actually has Administrator rights for a while, then he/she no longer has those rights. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b3e4ccb6-9ca1-49aa-8b6e-aa675774a8ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
