|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Stephen: User.getOrCreate uses keyFor(String) which by default lowercases the user name in the case-insensitive strategy.
But the authorization strategy is configured for uppercase user names, and there never was a need before to do case insensitive comparison.
E.g. https://github.com/jenkinsci/role-strategy-plugin/blob/master/src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleMap.java#L71
So, no permissions for the newly lowercased user (even if he now retains his custom name, email address, password, ...)