You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Goals
Non-Goals
No response
Background
So there is a problem and a few questions about making custom SingIn pages.
Basically, docs describe how to create: 1. Page with 2. buttons that 3. redirect to signIn pages (Like Magic Links or OAuth).
The problem is that most website have different flow of logging in user.
The typical website has navbar with ink to Login page:
Now after clicking on Login we should be redirected to page with Email input and "Send" button
One page, one email form.
After filling in the email user should be redirected to:
To implement it, one could do this:
(My understanding is that if csrfToken and cookie would be fetched server side
and inserted into form on page load then Javascript woudn't be needed)
It seems that this implementation is safe.
This flow should be a default for Sign-In pages.
Proposal
This should be in docs in Custom Sign in pages, at least, or a default flow for every provider/page.
Beta Was this translation helpful? Give feedback.
All reactions