-
-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
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
Magic Link Flow Questions #406
Comments
@shiftlabs1 when magic link login flow is used.
You can set the redirect URL by either passing it to the magic_link login param or by setting the |
thanks @lakhansamani . None of this in the docs .Would need adding . |
True, |
@lakhansamani I am back at this . The redirect URl i get only has querystring parameter "roles" and nothing more. How do i get the user's auth data as expected to redirect them as logged in users |
I got this for e.g
|
Looking at the code
redirect Url should also get the token passed as query string to enable a call to getprofile (i am assuming the token is access token) for e.g to pull the current user's credential and also mark them as logged in |
@lakhansamani please take a look at this and let me know how to proceed. |
@shiftlabs1 I am quite not getting the flow here, Can you write down the flow once and reproducible steps Thanks |
The current flow is
Ideal should be from 4 above right now the redirectUrl being behind an auth wall just send the user back to the login screen . |
@lakhansamani , I should be able to do this from the redirect URL |
Thank you for sharing the reproducible steps, |
@lakhansamani ,I am trying to make sense of the magic link flow. When a user clicks on the link in their email , what happens next ? what authorizer function do we call on our application to verify the incoming link ? Does it have a token attached? are we supposed to call verifyEmail and pass a token parameters from the URl like we do in the SIgn up Flow ? There is no where in the documentation (or any of the youtube videos) explaining this bit
The text was updated successfully, but these errors were encountered: