We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email addresses are optional. Very bad things happen if we treat all users who have no email address as the same user.
Example:
$RT::Config::ValidateUserEmailAddresses
'[email protected]'
Suppose RT::Interface::Web::AttemptExternalAuth() calls
RT::Interface::Web::AttemptExternalAuth()
$UserObj->Create(Name => ..., Gecos => ...);
The call will fail, since the call gets canonicalized to
$UserObj->Create( Name => ..., Gecos => ..., EmailAddress => '[email protected]' );
and RT::User::ValidateUserEmailAddress() will reject it with an "Email address in use" error.
RT::User::ValidateUserEmailAddress()
"Email address in use"
The text was updated successfully, but these errors were encountered:
Bug report also filed as https://rt.cpan.org/Ticket/Display.html?id=115494
Sorry, something went wrong.
No branches or pull requests
Email addresses are optional. Very bad things happen if we treat all users who have no email address as the same user.
Example:
$RT::Config::ValidateUserEmailAddresses
is enabled (as per default)'[email protected]'
.Suppose
RT::Interface::Web::AttemptExternalAuth()
callsThe call will fail, since the call gets canonicalized to
and
RT::User::ValidateUserEmailAddress()
will reject it with an"Email address in use"
error.The text was updated successfully, but these errors were encountered: