-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Low
-
None
-
13
-
Severity 3 - Minor
-
4
Issue Summary
When an email is firstly invited as a customer and then as an Atlassian Account, they will end up with duplicated accounts. Customers in that condition will be asked to "Login with single sign-on" because of the Atlassian Account. If the Atlassian account is then disabled, Jira will still ask the user to "Login with single sign-on" even if the only active account now is the portal only one, which authenticates directly in Jira with username and password.
Steps to Reproduce
- Create a portal only account;
- Invite the same email as an Atlassian Account;
- Disable the Atlassian Account;
- Try to log in to the customer portal.
Expected Results
Jira will present the password field since the Atlassian Account is disabled and the email is now a portal only account.
Actual Results
Jira still asks the customer to "Login with single sign-on", but since the Atlassian account is disabled, they won't be able to log into the portal.
Workaround
Delete the Atlassian Account at <instance>.atlassian.com/admin or migrate the customer account to Atlassian Account and remove all the application accesses.
- mentioned in
-
Page Loading...