Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Verification email landing page needs to provide appropriate messaging on "what to do next" #309

Closed
ckarlof opened this issue Nov 14, 2013 · 6 comments
Assignees

Comments

@ckarlof
Copy link
Contributor

ckarlof commented Nov 14, 2013

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=oz

@jbonacci
Copy link

👍 to this idea.

@rfk
Copy link
Contributor

rfk commented Nov 14, 2013

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.

@ckarlof
Copy link
Contributor Author

ckarlof commented Nov 14, 2013

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.

@pdehaan
Copy link
Contributor

pdehaan commented Nov 26, 2013

@rfk to move to fxa-content-server /cc @pdehaan

@rfk
Copy link
Contributor

rfk commented Nov 26, 2013

@rfk to migrate the rest of this bug into the fxa-content-server repo

@rfk
Copy link
Contributor

rfk commented Nov 27, 2013

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 rfk closed this as completed Nov 27, 2013
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.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants