There have been several issues resolved recently with regards to case sensitivity of user name within Jenkins authentication. However, I am not certain that the current state is behaving as one would expect.

Our users sometimes report that when logging in to Jenkins they are recognised, but no jobs are visible. We have found that the user has not matched the case as specified within the Security Matrix row.

For example, we set up a user within the security matrix as A123 and give them their permissions. When they log in (autheticated via LDAP) as A123 there is no issue. If they log on with a123 they are still authenticated (because the LDAP authentication correctly ignores the case), but Jenkins security then fails to match due to the case difference.

We know we can try a work around by adding two identical records to the matrix: a123 and A123. But with many users, that becomes a bit of a nightmare.

For now we have put in a banner to say - "See no jobs? Log in with an upper case user id". But I am guessing this is something that could be improved to bury the case sensitive issues for good?

Maybe I'm missing a checkbox or something?!?