Is there any activity or planned activity on this? After upgrading to Jenkins 1.596 and getting the latest version of the matrix auth strategy plugin, we had to make, what I would consider unnecessary,changes to our Jenkins configuration to support camel-case usernames. Jenkins supports case-insensitive login names so this plugin should, too.

Any Progress on this issue.

Please check on this...

There is a fairly easy workaround for this issue: Have your users log in using the user name case used in the permissions config. Use e.g. Simple Theme Plugin to add a note to the login page.

For any higher priority, please explain the reasoning. "I really want it fixed" is not a good reason

For us, this is a minor issue that is going to rear its head a number of times. Currently, we have a mix of upper/lower case AD group names. If we set a job to the wrong case, the user can't access it. Whats worse, a user may have access on multiple groups of jobs so if we set the right case on one and not on the other, its sometimes a mystery why it isn't working until we remember this gotcha.

It's not a show stopper by any means but it surely is annoying. Luckily, we dont have this issue with the case sensitivity of the user name but we do have this issue with the setting the groups.

One area where this can REALLY be a problem is if you are overriding a parent matrix security setting. Its very easy to accidentally lock yourself out of the job if you put in your administrative ad group in the wrong case. Yes, I know you can go and modify the job config to fix the issue but I shouldn't have to get on my server every time I spell my group with 'd' instead of 'D'.

There seem to be a bug in the org.acegisecurity:acegi-security:1.0.7 (2008) lib used by the jenkins-ldap-plugin.

It reuses the username provided by the login screen instead of loading it from the ldap record (see below).

The recent versions of spring-security-ldap don't reuse the username, they reload the username from the LDAP record (see BindAuthenticator#bindWithDn().

See org.acegisecurity.ldap.search.FilterBasedLdapUserSearch#searchForUser

public LdapUserDetails searchForUser(String username) {
    if (logger.isDebugEnabled()) {
        logger.debug("Searching for user '" + username + "', with user search "
            + this.toString());
    }

    LdapTemplate template = new LdapTemplate(initialDirContextFactory);

    template.setSearchControls(searchControls);

    try {
        LdapUserDetailsImpl.Essence user = (LdapUserDetailsImpl.Essence) template.searchForSingleEntry(searchBase,
                searchFilter, new String[] {username}, userDetailsMapper);
        user.setUsername(username);

        return user.createUserDetails();
    } catch (IncorrectResultSizeDataAccessException notFound) {
        if (notFound.getActualSize() == 0) {
            throw new UsernameNotFoundException("User " + username + " not found in directory.");
        }
        // Search should never return multiple results if properly configured, so just rethrow
        throw notFound;
    }
}

AFAICT, this duplicates JENKINS-23805 which was released as matrix-auth-1.7. Please correct me if I'm wrong.