Details
-
Bug
-
Resolution: Fixed
-
Medium
-
6.0.2, 6.0.3
-
6
-
Description
Steps to Reproduce (these are the steps received from customers)
- Upgrade to JIRA 6.0
- Attempt to login to JIRA
Expected Results
- Login is successful
Actual Results
Login fails with the below exception:
java.lang.IllegalStateException: User 'xxxx' exists but has no unique key mapping. at com.atlassian.jira.user.util.DefaultUserManager.getUserByName(DefaultUserManager.java:262) at com.atlassian.jira.security.login.JiraSeraphAuthenticator.getUser(JiraSeraphAuthenticator.java:36) at com.atlassian.seraph.auth.DefaultAuthenticator.login(DefaultAuthenticator.java:101) at com.atlassian.seraph.filter.PasswordBasedLoginFilter.runAuthentication(PasswordBasedLoginFilter.java:127)
Workaround
Refer to our JIRA Login Fails With the Message - User exists but has no unique key mapping KB for the workaround.
Attachments
Issue Links
- causes
-
JSWSERVER-9642 GhUpgradeTask003 is failing, throwing a java.lang.NullPointerException
- Closed
- is caused by
-
JRASERVER-33679 Plugin upgrades run even when JIRA upgrades don't
- Closed
-
JRADEV-22455 Loading...
- is duplicated by
-
JRASERVER-34019 User 'XXXX' exists but has no unique key mapping - JIRA-33557
- Closed
- is related to
-
JSWSERVER-9697 Upgrading GreenHopper results in a NullPointerException on GhUpgradeTask032.upgradeClassicContextAssignees
- Closed
- relates to
-
JRASERVER-30983 EAP Feedback - JIRA 6.0
- Closed
- was cloned as
-
JRASERVER-59131 JIRA Login Fails With the Message - User xxxx has no unique key mapping
- Closed
- is cloned from
-
JRADEV-22190 Loading...