This repository has been archived by the owner. It is now read-only.
Cannot send unblock code if using the wrong email case #4467
Assignees
Labels
Comments
shane-tomlinson
pushed a commit
that referenced
this issue
Nov 28, 2016
Signin unblock is broken if the user types their email using different casing to when they signed up. The auth server returns an error that says "Feature not enabled". This fixes that by updating the model with the email that is returned by the server if it returns an INCORRECT_EMAIL_CASE error. Unfortunately, the sync v3 functional test fails, trying to figure out why. fixes #3893 fixes #4467
shane-tomlinson
pushed a commit
that referenced
this issue
Nov 29, 2016
Signin unblock is broken if the user types their email using different casing to when they signed up. The auth server returns an error that says "Feature not enabled". This fixes that by updating the model with the email that is returned by the server if it returns an INCORRECT_EMAIL_CASE error. Unfortunately, the sync v3 functional test fails, trying to figure out why. fixes #3893 fixes #4467
shane-tomlinson
pushed a commit
that referenced
this issue
Nov 29, 2016
Signin unblock is broken if the user types their email using different casing to when they signed up. The auth server returns an error that says "Feature not enabled". This fixes that by updating the model with the email that is returned by the server if it returns an INCORRECT_EMAIL_CASE error. Unfortunately, the sync v3 functional test fails, trying to figure out why. fixes #3893 fixes #4467
shane-tomlinson
pushed a commit
that referenced
this issue
Nov 29, 2016
Signin unblock is broken if the user types their email using different casing to when they signed up. The auth server returns an error that says "Feature not enabled". This fixes that by updating the model with the email that is returned by the server if it returns an INCORRECT_EMAIL_CASE error. Unfortunately, the sync v3 functional test fails, trying to figure out why. fixes #3893 fixes #4467
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Copied over from mozilla/fxa-auth-server#1573
/account/login/send_unblock_code responds with http response 503, error number 202, "feature not enabled"
STR
block123@restmail.netBLOCK123@restmail.netblock123@restmail.net, everything works as expected.Response to /account/login using
BLOCK123@restmail.netResponse to /account/login/send_unblock_code using
BLOCK123@restmail.netRef mozilla/fxa-auth-server#1570
A content-server only fix is to use the normalized email returned to the first call to
signIn. We'll have to set skipCaseError=true to retry ourselves and get access to the email.The text was updated successfully, but these errors were encountered: