Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.12.1
-
8
-
Severity 2 - Major
-
4
-
Description
Hello, everyone! After comparing this bug request against the known bug report JSDSERVER-5786: Service Desk customer sign up/password reset page does not indicate if the password does not meet the password policy requirements we realized that both are addressing the same error with a slightly different scenario which is during account creation. We will be closing this request now and will ask you to cast your votes and add any additional feedback so we can have the impact of this issue gathered in one single request.
Best regards,
Amirul
Summary
Service Desk customer sign up page does not indicate why account cannot be created
Environment
- Jira Service Desk 3.12.1
- Jira is using a read-only LDAP directory in the top ordered position
- Jira Service Desk does have public sign up enabled, both for the system and for this project.
Steps to Reproduce
- As a new JSD customer, go to the login page http://localhost:8791/servicedesk/customer/portal/1/user/login?destination=portal%2F1
- click the "Sign up for an Account" link http://localhost:8791/servicedesk/customer/portal/1/user/signup
- Enter in email address, password, and full name, then click 'Sign Up'
Expected Results (end user)
Account should be created
OR
A clear error message needs to be displayed to the end user to explain why account was not created.
Actual Results (end user)
- Nothing happens on the page
- User is not able to create an account
- only by looking into the browser's console when trying to click the signup button, is there an error generated such as:
{"errors":[],"reasonKey":"Signup is not currently available","reasonCode":"400"}
Notes
We need to be more communicative with the end user to explain why they cannot create an account right now. If this is a JSD specific setting preventing this, then the error message displayed on the screen should say so. If it is a problem that stems from the Jira server settings like in this case, then the error message displayed should convey this detail.
Workaround
The Jira administrator will have to
- Change the order of the user directories so that the read-only directory is not in the top/first position
Attachments
Issue Links
- is related to
-
JSDSERVER-7060 Some Service Desk functionalities not working as expected when Jira is connected to an LDAP server that's temporarily not reachable
- Gathering Impact
- relates to
-
JSDSERVER-5786 Service Desk customer sign up/password reset page does not indicate if the password does not meet the password policy requirements
- Closed
- is cloned by
-
JSMDC-6086 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...