-
Bug
-
Resolution: Won't Fix
-
Medium
-
Severity 2 - Major
-
Summary
- When trying to reset a customer password via the JIRA Service Desk Project > Customers tab, the JIRA Service Desk administrator is directed to User Management e.g. https://INSTANCE_NAME.atlassian.net/admin/users/view?username=CUSTOMER_EMAIL_ADDRESS.
- Password reset email is sent, but the URL in the password reset link resets the customer's Atlassian ID password.
- JIRA Service Desk customers do not authenticate using Atlassian ID.
- The password reset feature has no effect on the JIRA Service Desk customer account - the password on a customer account(portal only) stays the same.
Environment
- JSD 1000.1313.0
Steps to Reproduce.
- Create new customer in JSD.
- Customer accepts invitation sent via email.
- Customer sets a "Display name" and password e.g. "Password123".
- JIRA Service Desk admin resets customer password by hovering the mouse pointer over the customer account; More > Administer. The JIRA Service Desk Admin is directed to User Management(https://INSTANCE_NAME.atlassian.net/admin/users/view?username=CUSTOMER_EMAIL_ADDRESS).
- Password email sent to customer.
- If customer doesn't have an Atlassian ID, customer is prompted to sign up for an Atlassian ID. If the customer has an Atlassian ID, then the customer is prompted to reset the Atlassian ID password.
- After the customer sets a new password.
- Customer tries to log into the Service Desk Portal with new credentials - login fails.
Expected Results
- Password is reset and access to the Service Desk Portal is granted.
Actual Results
- Customer receives an error message: "Sorry, your email and password are incorrect - please try again."
- Access is not granted.
Notes
- Using the original password("Password123" in our example) that was set will allow the customer to log into the Service Desk Portal.
- The password reset feature has no effect on the JIRA Service Desk customer account.
Workaround
- Navigate to: https://INSTANCE_NAME.atlassian.net/admin/jira-service-desk/portal-only-customers/view?username=USERNAME (in most cases the email address is the username) and update the customer's password from there
The root problem here is that the original user edit link still works, but shows a broken experience. We are soon completing the Identity Platform migration, at which point the link will cease to work and that should clear up the confusion mentioned in this ticket