Skip to content

Don't lookup empty email when canonicalizing#3

Open
dpoon wants to merge 1 commit into
bestpractical:masterfrom
dpoon:master
Open

Don't lookup empty email when canonicalizing#3
dpoon wants to merge 1 commit into
bestpractical:masterfrom
dpoon:master

Conversation

@dpoon
Copy link
Copy Markdown

@dpoon dpoon commented Jun 15, 2016

Fix for Issue #2

Email addresses are optional.  Very bad things happen if we treat all
users who have no email address as the same user.

Example:

1. $RT::Config::ValidateUserEmailAddresses is enabled (as per default)
2. There exists user "A" whose EmailAddress is empty.
3. There exists user "B" whose EmailAddress is 'b@example.org'.
4. User A is merged into User B.

Suppose RT::Interface::Web::AttemptExternalAuth() calls

    $UserObj->Create(Name => ..., Gecos => ...);

The call will fail, since the call gets canonicalized to

    $UserObj->Create(
        Name => ..., Gecos => ...,
        EmailAddress => 'b@example.org'
    );

and RT::User::ValidateUserEmailAddress() will reject it with an
"Email address in use" error.

This commit changes CanonicalizeEmailAddress() so that it does not try
to rewrite an empty address.  In addition, a conditional has been
rewritten to avoid a double negative and an excessively long line.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant