• Type: Suggestion
• Resolution: Duplicate
• Component/s: Accounts Integration (Signup, Invite Team, Login, Logout, Reset Password, Profile)
• Labels:

  • affects-server
  • cs

[JSDCLOUD-3669] Allow email domain restrictions for public signup

BK Paton made changes - 17/May/2021 8:11 AM

Remote Link

New: This issue links to "Page (Confluence)" [ 552995 ]

shihab made changes - 27/Apr/2021 5:06 AM

Labels

Original: affects-server

New: affects-server cs

BK Paton made changes - 06/Dec/2020 9:40 PM

Resolution		New: Duplicate [ 3 ]
Status	Original: Gathering Interest [ 11772 ]	New: Closed [ 6 ]

BK Paton made changes - 06/Dec/2020 9:40 PM

Description

Original: {panel:bgColor=#e7f4fa}   *NOTE:* This suggestion is for *JIRA Service Desk Cloud*. Using *JIRA Service Desk Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDSERVER-3669].   {panel} h3. Problem Definition In certain cases, Service Desks need to be restricted to a set of customers belonging to one and the same organisation. Public signup does not provide a proper means to prevent incorrect customer accounts not belonging to that organisation from being created. The only alternative available right now, is to disable public signup, which has as a result that the Service Desk administrator can get presented with significant amounts of work solely for account creation. h3. Suggested Solution As such, being able to define an email domain as requirement for public signup, can provide a small degree of safety, while at the same time prevent a lot of overhead for the administrators. For instance, if a Service Desk has public signup enabled, and an email domain has been defined, the Service Desk will only allow account creation if the source address conforms to the defined domain.

New: {panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Cloud*. Using *JIRA Service Desk Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDSERVER-3669]. {panel} {panel:title=Update from Atlassian Product team} Thank you all for your votes and feedback on this issue. This is the smaller of two issues about the same topic, and has been closed to direct the discussion to https://jira.atlassian.com/browse/JSDCLOUD-868 That issue in currently _Under Consideration_ and being evaluated for prioritisation. We would love to hear from you over there. {panel} h3. Problem Definition In certain cases, Service Desks need to be restricted to a set of customers belonging to one and the same organisation.  Public signup does not provide a proper means to prevent incorrect customer accounts not belonging to that organisation from being created. The only alternative available right now, is to disable public signup, which has as a result that the Service Desk administrator can get presented with significant amounts of work solely for account creation. h3. Suggested Solution As such, being able to define an email domain as requirement for public signup, can provide a small degree of safety, while at the same time prevent a lot of overhead for the administrators. For instance, if a Service Desk has public signup enabled, and an email domain has been defined, the Service Desk will only allow account creation if the source address conforms to the defined domain.

BK Paton made changes - 06/Dec/2020 9:37 PM

Assignee

Original: Amaresh Ray [ aray2@atlassian.com ]

New: BK Paton [ 7ad1551c39c0 ]

Christopher made changes - 04/Dec/2020 2:49 AM

Component/s

Original: Email - Incoming [ 46704 ]

Andrea made changes - 18/Nov/2020 5:25 AM

Remote Link

New: This issue links to "Page (Confluence)" [ 516101 ]

SET Analytics Bot made changes - 06/Nov/2020 12:53 AM

UIS

Original: 13

New: 16

SET Analytics Bot made changes - 30/Oct/2020 12:38 AM

UIS

Original: 12

New: 13

SET Analytics Bot made changes - 24/Oct/2020 12:53 AM

UIS

Original: 10

New: 12

Load more older events