-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
7
-
Use Case
JSD is used in one company as an internal helpdesk center, only. All "customers" are already known and can already log in. From former times, they are also used to send emails for raising issues. By enabling "Email Requests" also the public sign up feature is enabled.
Problem
Some of the customers landing on the portal login page are confused by the link "Sign up for an account" and create a 2nd account. Agents have extra efforts.
Work-a-Round
1) Blocking the sign up page by adding a "Context" element in server.xml or any equivalent on the reverse proxy side. This just works when the customer presses "Submit". Page is not blocked upfront. Following error is then shown: "We are unable to submit your request. Please refresh the page and try again. ...".
2) install SSO, so the customer will (almost) never see the login page.
Solution
Add somewhere (at the customize sidebar?) a checkbox, that simply hides / disables this sign up link with its descriptive text.
- links to
[JSDSERVER-6474] Configuration to hide/disable "Sign up for an account" link
Hi c2ba03691089
If all the customers are already known can you use the setting "Customers who have an account on this Jira site" for "Who can raise requests?" on customer permissions page.
Requests by email should work regardless of the customer permission setting. When you select "Customers who have an account on this Jira site" only existing customers will be able to create email requests.
Can you give us more details on your use case?
Thanks,
Kunal
JSM Team
@kkanojia
the site is not exposed to the internet. Most requests are created by known internal users but we have the plugin "Email this issue" which fetches mails from a mail server and creates issues. When the sender is unknown, an account is generated. So we can't set to "Customers who have an account on this Jira site", thus they cannot not be the reporter of one issue.
In our use case, we simply do not need the link "signup for an account" on the portal. But internal users can abuse it to create accounts with nonsense addresses. Therefore a configuration topic would be fine to remove this link from the portal. Blocking the signup URL by the reverse proxy does not work anymore.