Username changes to all caps after logging in

Still need help?

The Atlassian Community is here for you.

Ask the community


After logging into an instance if JIRA, the user's username changes from lowercase characters to uppercase characters.

For example, the username was fluffhead123 prior to login.  After login, the username appears as FLUFFHEAD123.


This is caused by JIRA's integration with an LDAP directory for delegated authentication.  In some cases, organizations will have a user provisioning process where an account is created in JIRA before it is created in their LDAP server.  The account's username could be entered into JIRA as fluffhead123, but when the LDAP account is created, it has FLUFFHEAD123 listed as its relative distinguished name (username).  When the user logs in, their account is then updated with the all caps version of their username.  Because most LDAP systems and are not case sensitive, the user can still log in with the lower case version of their username.  

The change in username casing does not have a major impact on the performance of any of JIRA's core functionality with the noted exception of any Activity Stream gadgets that have been configured to filter on a specific username.  This gadget is, at the time of this writing, case sensitive and will stop pulling activity records for that user. 


(info) As noted, the change in username casing should not present problems with core JIRA functionality. Since LDAP systems are frequently used as the systems of record within an organization, a JIRA admin who finds themselves in this situation needs to reach out to the administrators of the relevant LDAP system for more information.

Last modified on Feb 26, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.