The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Enforce Push Author Stash Hook

Seth Carter
October 23, 2014

What special case does checking the "Allow alternate email (<username>@)" check box allow for?

The obvious assumption is that it allows an alternate email but wouldn't that directly oppose the default check "Require matching email address (required)" which cannot be turned off?

Thanks,
Seth 

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Michael Heemskerk
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 24, 2014

Seth,

The logic appears to be a bit more subtle. When the 'Allow alternate email' check box is checked, the hook will allow two email addresses:

  • The one that is configured in the user directory (could be the LDAP directory)
  • The one that matches username@domain.configured.in.user.directory

For instance say that your username is scarter and your email address according to LDAP is seth.carter@company.com

Without the checkbox checked, only commits authored by seth.carter@company.com would be allowed.

With the checkbox checked, both seth.carter@company.com and scarter@company.com would be allowed.

 

0 votes
Seth Carter
November 11, 2014

Thanks Michael, while it isn't what I wanted it to be it does explain what it actually does!

TAGS
AUG Leaders

Atlassian Community Events