This repository has been archived by the owner. It is now read-only.
Support pre-verified emails in /account/create #1540
Closed
Assignees
Comments
shane-tomlinson
pushed a commit
that referenced
this issue
Aug 28, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. fixes #1540
shane-tomlinson
pushed a commit
that referenced
this issue
Aug 28, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. This PR also introduces the concept of a "Relier" model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540
shane-tomlinson
pushed a commit
that referenced
this issue
Aug 28, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. This PR also introduces the concept of a "Relier" model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540
shane-tomlinson
pushed a commit
that referenced
this issue
Aug 28, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. This PR also introduces the concept of a "Relier" model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540
shane-tomlinson
pushed a commit
that referenced
this issue
Aug 28, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. This PR also introduces the concept of a "Relier" model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540
shane-tomlinson
pushed a commit
that referenced
this issue
Sep 4, 2014
`preVerifyToken` is sent by trusted RPs to indicate that a user is already verified. The Auth Server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the `/signup_complete` screen. If the pre-verification fails, the user is still requried to verify their email address as is currently done. This PR also introduces the concept of a "Relier" model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540
|
Fixed by #1606 |
ckarlof
added a commit
that referenced
this issue
Sep 5, 2014
feat(client): Add support for `preVerifyToken`. A preVerifyToken is sent by trusted RPs to indicate that a user is already verified. The auth server then does a dance with the trusted RP to determine whether to create an account for the user without the need to verify their email address. If the user is pre-verified, the signup flow completes at the /signup_complete screen. If the pre-verification fails, the user is still required to verify their email address as is currently done. See https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#preverifytoken for further information on preVerifyTokens. This PR also introduces the concept of a Relier model. A Relier is a model that represents an RP and information about/from the RP. fixes #1540 r=ckarlof,nchapman
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Marketplace is in the process of migrating from Persona to FxA for authentication. One migration case they want to make easier is when the user is already authenticated with a verified Persona account. In this case, they want to bypass the email verification step when user creates a FxA, because the user presumably already verified her email via Persona.
The content server work would be to support this API change in the FxA auth server.
preVerifiedTokenpreVerifiedTokeninto account creation105and resubmit account creation withoutpreVerifiedTokenpreVerifiedTokenwas acceptedThe text was updated successfully, but these errors were encountered: