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
Let's say I have a sign-in page where I have a form where I can make a choice which would be used when creating the session JWT. When using credentials flow (for instance, email & password), I can take the value directly from the request data. But when using OAuth, the original request data is lost after the redirections.
I guess the state object could be used to include arbitrary data through the authorization process, but as far as I know, next-auth doesn't support adding own data to it. Is there any other way around it?
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
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say I have a sign-in page where I have a form where I can make a choice which would be used when creating the session JWT. When using credentials flow (for instance, email & password), I can take the value directly from the request data. But when using OAuth, the original request data is lost after the redirections.
I guess the
state
object could be used to include arbitrary data through the authorization process, but as far as I know, next-auth doesn't support adding own data to it. Is there any other way around it?Beta Was this translation helpful? Give feedback.
All reactions