Can I allow users to create accounts on Jira only if they email matches a specific domain?

[Sorin Sbarnea (Citrix)]

I am looking for a setup of a limited-public Jira: one where anyone from inside the company should be able to create an account, and where people from outside the company have to request acces.

The current private mode asks for too much account creation tasks received for people from inside the company.

[Andy Brook [Plugin People]]

Hi Sorin,

I always thought this would be handy in JEMH, so I've now implemented the necessary support in JEMH 1.4.14 (not released just yet, doco needed). It solves your use case as follows:

1. Email sent from remote party is sent to JEMH, the sender email address matches user creation whitelist filter as a domain regexp (thereby addressing your filtering requirement)

2. JEMH Profile has 'require signup' checked, and has the new UserSignupFilter enabled, notices the remote sender is not associated with a JIRA user. An email is sent to the user containing a HTTP link to a JEMH REST service, with a generated GUID as a param. Teh email is marked as 'On Hold' and not processed, stored in Audit History.

3. The User clicks the link in their signup email, and the JEMH userSignup REST service is triggered, locating the GUID match to confirm a request was received, then creating a user account, and finally, the good bit, locating all email received from that user until now, from JEMH Audit History, and re-animates them against the related Profile.

- Each link is valid for hardwired 30minutes

- Notifications are of course wrapped in JEMH TemplateSets so you can customize, on a per-Profile basis.

- Failure to 'click' results in the related On Hold emails being garbage collected through automated Audit History puring.

How do you see this working for you?