I have a public Jira instance that allows people to register to create new accounts, but the same instance is used by internal people that are using LDAP to authenticate.
The main problem is how to prevent people from outside from creating accounts with the same name as ones from intranet?
Here is a client-side restriction that works if you add this code to the Annoucement Banner in admin pannel.
Still rememeber that this is only client side, so people can go around this if they really want.
Use the JIRA REST API to search for users with the username used to register and reject if a result returns from the REST search. Does this work for you?
A plugin will probably do.
I would support the option of
"force a specific pattern (regexp) for creation of local accounts."
The other option with the email addresses
"even better allow, people to login using their email address (email as login). I know that this could be a problem if you have several accounts with the same email, something that currently is possible in Jira, even if I wish not to be possible."
seems prone to errors, so I would not recommend it.
In addition to above options, you could write a plugin in order to achieve this. If your team does not have the expertise to implement this, you could contact one of our Experts who are professionals in implementing requirements like these.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs