We're using the miniOrange plugin to connect to our Shibboleth

We put SSO in front of ours (restricting the portal), then created a mailbox rule to delete emails that didn't match our preferred domain.  

Which SSO/IdP?

@Shanelle, good idea! I was thinking on a solution in JSD but at the end, it can be restricted at mailbox side! I have to check it.

Thank you

We put SSO in front of ours (restricting the portal), then created a mailbox rule to delete emails that didn't match our preferred domain.  

Hi,

I have found a workaround here (based on ScriptRunner): 

https://community.atlassian.com/t5/Jira-Service-Desk-questions/Restrict-Service-Desk-Portal-signup-to-a-specific-Domain/qaq-p/782699

Does anybody know any other alternative/workaround?

Thank you

Let's vote on both so our votes aren't divided. 

Also seen here https://jira.atlassian.com/browse/JSDCLOUD-868?_ga=2.68453969.1348442297.1568828945-1525777402.1568828945

We are also waiting for this feature. Please implement.

This is unbelievable, EVERY Help Desk software product I have used, and I have used many, has this feature (to whitelist one, or multiple domains when fetching email). This feature is SUPER important to IT Managers and Sys Admins. How could you miss this Allassian? And it's been on the boards for almost 4 years now?!!!?! since 2014?!???!  UUgggghhhhhh  Glad I didn't pay for it yet, I'll prob jump ship, very very disappointed....

Hmm, issue is unassigned after 3.5 years. Not a good sign. Can anyone from Atlassian provide a comment? If this will not be implemented, it would at least be nice to know that.

no updates so far?

Crazy that this is not implemented yet, I assumed JSD would have had this functionality from the beginning. Meanwhile this request has been open for over three years. Please prioritise this.

I would very appreciate this!

This feature is the only one holding us back from using JIRA Cloud based Service Desk. +1

This would be a really helpful feature! +1

That would be realy helpful for us as well and would be able to use Service Desk also in our DMZ instances.

This is another case where Atlassian could add a key security feature rather easily, but will not do the right thing. How hard would it be for the JSD registration logic to check the supplied email address against a list of domains? It's like 10 lines of code. 

We have the same problem that everyone else has mentioned. We are unable to allow public signup with JSD while also restricting by domain to ensure that our knowledge base isn't available for anyone with a gmail hotmail or other generic email to see. Please implement this, you're forcing customers to choose between having to register all their JSD users manually every time someone new joins the company, or to have a security vulnerability by exposing their IP, neither of which seems like an acceptable option for a large organization that's paying for this product expecting it to be as simple and secure as the videos make it seem.

Completely agree. Our users have multiple email addresses and the last thing we want to do is miss a service desk request from them. We want the public option but with our JIRA/Service Desk on the internet we can't use it. Either restrict who can sign up based on email domain or give the option to remove the sign-up option on the portal.

Alternatively, if JIRA/Service Desk read the ProxyAddress attribute from Active Directory users could have multiple email addresses associated with their accounts

Cannot restrict customer public signup for Service Desk only to a specific set of external customers/domains, By selecting option Under [Site Administration --> Sign up options --> Restricted by domain(s)] it says "Only people with an email address that matches the specified domain(s) can sign up." But is not working when a domain name is entered. My company will simply not be able to use the Service desk unless we can secure signup email addresses based on domain name. Also, "Notify administrators by email when an account is created by create or sign up" is not working. https://jira.atlassian.com/browse/JSD-868 was created on 25/Sep/2014 and it is disappointing to see it has not been addressed since then.

We have a service desk in which we've enabled public signup, so that we don't miss tickets which are emailed to our channel from unregistered users. This works well, but also means that competitors can easily enroll in our service desk and browse our knowledge base. We're screening the user lists regularly but this method leaves a lot to be desired.

Most unauthorized traffic is hidden behind the anonymity of a gmail/hotmail account. A blacklist would be a big help in better securing our assets

Link to original post to atlassian answers here :
https://answers.atlassian.com/questions/38381072/how-to-better-protect-my-service-desk-and-knowledge-base-from-unwanted-visitors-and-competitors

This is a really critical feature and I'm shocked that it has not yet been implemented, especially given that it is implemented for JIRA Software and Confluence. We have a large organization and I cannot realistically encourage people to use Service Desk if my team has to create an account for them; however, we are also receiving spam and service tickets created by robots. In the latest incident, someone created a ticket and tagged 80 people from our organization in the ticket, prompting widespread confusion. Again, this is a critical feature that must be implemented soon or we will be forced to discontinue use of Service Desk.

This was issue created 1.5 years ago... are we ever going to see it implemented?

I agree that this is a critical feature for service and consulting companies using the suite of Atlassian products.

This is a critical future, the product is unusable with out it. My company will simply not be able to use the help desk or the knowledge base unless we can secure signup email addresses based on domain name. Oh, and got to make sure to send an alert email to admins for every sign up - this is too left out!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi

This is there in confluence. Why not in JSD? Would be very helpful to have it in JSD too

Thanks

This is a no-brainer add for any customer service organization/help desk structure. You need to simplify service desk administration by allowing entire organizations to access the desk without having to 'opt-in' and sign up. The records of those users (customers) will end up inside Jira regardless, so the long tedious process of getting everyone to 'sign up' can be fast-tracked.

This is a critical feature I feel has been left out of the product!
Having to manage a customer list by assigning logins is painful! We need to have a way to specify by email domain name, which are valid for registration.

Myself and my company would like this feature as well.

For me it would be enough if I could blacklist single domains from registration and still enable everyone else. A simple textfield with one Domain per line would be great.

*@foobar.org
*@example.com
*@ithinkyouunderstandwhatiwant.gov

That would help me A LOT!

+1 This would be HUGE for my use of JIRA service desk. Right now I have no option but to choose wide open public sign-ups which I am not thrilled about. It would be great to be able to add a domain name when I bring a new customer on and not have to deal with requests from non-customers.

Any progress on this possibly getting addressed in the future?

+ 1 from me; this is required because if we truly want a self service portal, we need to be able to secure the sign on by restricting what domains can sign up.

+1. This is must have for support portal. Lack of this feature is only critical issue with SD that forcing us to move to competitor.

I vote for this feature. In SD you have the following settings for the portal:

Everyone with an account can access my Customer Portal

• Anyone can sign up for a customer account on my Customer Portal

Only people on my customer list can access my Customer Portal

In our case, we selected the following option, as we don't want to be burdened with having to add users to the list as the other option asks for.

Everyone with an account can access my Customer Portal

• Anyone can sign up for a customer account on my Customer Portal

Then in the SignUp options, we selected the following option, which restricts people with domains not set in this section. I assumed this would prevent these, but it looks like it doesn's, which makes no sense.

Restricted by domain(s)
Only people with an email address that matches the specified domain(s) can sign up.

I second this. We need to be able to limit the service desk signup to only customers who currently have a service contract with us.

Having this feature would be a big help for my company.