This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
Verification email landing page needs to provide appropriate messaging on "what to do next" #309
Comments
👍 to this idea. |
IIUC the verification landing page is provided by fx-content-server, not fx-auth-server. If we let it specify a dynamic URL for the verification page (per #308 (comment)) then it could tunnel this information through no worries. |
We don't need the entire URL to be dynamic (nor is it safe to do so). It might be sufficient to tack on a (vetted) "service" parameter received by the client to the email we send out. I don't think it needs to be persisted. |
@rfk to migrate the rest of this bug into the fxa-content-server repo |
Done: mozilla/fxa-content-server#95 I'm going to close it out from this end since #342 or something like it should fulfill our obligations here. |
rfk
pushed a commit
that referenced
this issue
Oct 24, 2018
…ed-tokens chore(logging): Log additional details for debugging expired tokens
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
E.g., on FxOS the user could create their FxA in Marketplace a flow, and then end up verifying their email on another device. FxOS team would like the ability for us to tell the user "what to do next" after completing verification. Thoughts on how to enable this? How about adding
service=<service name>
in the sign in or sign up flow so we know what service initiated the process? Google does something similar, FWIW: https://accounts.google.com/ServiceLogin?service=ozThe text was updated successfully, but these errors were encountered: