Yes that is a little more complicated.  We were able to allow public sign up again in June, and only users with the domain we whitelisted can sign up.  We do still have an organization set up though, so users can share with others in their org.
We still have to manually add all users to the org after they have created their account.  So it's 50% better with not needing to create accounts ourselves.

In our case we have 2 Service Desk configured.

Service Desk 1 is for External Users to submit issues regarding our Product, public signup is open.

Service Desk 2 is for internal users, to prevent external users from seeing the issues (or submitting issues) the only way we know of to accomplish this is to restrict it to Customers in an Organization. What we need is instead of having to add each and every user to the Organization just whitelist a domain, then anyone with a specific domain will be a customer in that organization.

I'm not seeing a difference between this request and another that is resolved. (https://jira.atlassian.com/browse/JSDCLOUD-868)  One is cloud and one is server, but it states that it affects both.

This has been available since May 2022, though my apologies if I'm missing a detail in this one that isn't included in the update.

https://community.atlassian.com/t5/Jira-Service-Management-articles/Use-email-domains-to-restrict-external-customer-sign-up-for-your/ba-p/2036372#M1710

This is highly needed, having to add customers 1 by 1 is time consuming and prevents adoption of Service Desk by the user base. All the suggested work arounds do not work for us. A simple *@domain.com allow would solve the problem.

All we need is to be able to whitelist email domains on user sign-up and if the user provided mail address not a member of a whitelisted domain, provide some pre-defined "sorry, you are not authorised" message.

I actually can't believe this ability doesn't exist.  Jira - do you have any idea how much of a headache this limitation is operationally?

...to give you a sense: the current alternatives offered are operationally labour intensive and pervasive enough to make us consider starting our service desk on a different product.

Hi,

it would be great to have public signup in Jira like it is in Confluence: a white list of email domains (our company and certain customers) which can signup by themselves not requiring a Jira administrator to do it for them.

We have linked our Confluence datacenter to Jira user directory.

If we let Jira handle public signup we can have Jira apply default groups to each new user - the same as if the user was created by an administrator. But Jira at this time cannot constrain public signup to administrator defined email domains.

On the other hand, if we let Confluence handle public signup we can constrain this to administrator defined email domains. But we are missing automaticly assigned default groups on signup in Confluence.

We have also looked into a possible purchase of Crowd. But from the documentation I read, Crowd has no public signup functionality of its own. So public signup from Confluence or Jira needs to be used - with the same results as without Crowd.

For us this is a mess which prevents us from public signup entirely.

Is there any solution?

Best Regards,

Lars

5 years later and no resolution what a joke!

Ensure for every customer coming to portal for sign up - the domain blocking should be remembered while allowing customer to do sign up.

for any domains which are not listed. It should call out that please login with valid domain id.

This way, the admin, setup responsibility is not custom made rules / automation which is not consistent from scalability point of view.

if the whitelisted domain is given just reject user creation and prompt them for additional CAPTCHA or other such challenges to avoid any DDOS

PS: Ensure this solution is given across to Server, DC, Cloud solutions

-Vijay Mane

+1 Highly needed!

+1