A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
you can also set redirect = false and catch response from signIn function :
redirect = false
signIn
const res = await signIn('credentials', { email, password, callbackUrl: `${window.location.origin}/account_page` redirect: false, } ) if (res?.error) handleError(res.error) if (res.url) router.push(res.url);
signIn return a Promise which has following structure :
{ error: string || undefined, status: number, ok: boolean, url: url || null }
you can check more on next-auth.js.org/getting-started/c...
How does this work? I have followed your example and am not getting any response in login page
You are not getting a response because the user isn't being set properly. The following code is able to handle Credentials (user & pass) and Providers auth, while setting jwt and session correctly.
callbacks: { jwt: async (token, user) => { if (user) { token.jwt = user.jwt; token.user = user.user; token.accessToken = user?.accessToken; } return Promise.resolve(token); }, session: async (session, token) => { session.jwt = token.jwt; session.accessToken = token.accessToken ? token.accessToken : session.user = token.user ? token.user : session.user; return Promise.resolve(session); }, },
Cool! Happy to see it has been added as a feature. Thanks for the update :)
Thank you so much! I hated that the function reloaded the page every time I submit the form
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
you can also set
redirect = false
and catch response fromsignIn
function :signIn
return a Promise which has following structure :you can check more on next-auth.js.org/getting-started/c...
How does this work?
I have followed your example and am not getting any response in login page
You are not getting a response because the user isn't being set properly. The following code is able to handle Credentials (user & pass) and Providers auth, while setting jwt and session correctly.
Cool! Happy to see it has been added as a feature. Thanks for the update :)
Thank you so much! I hated that the function reloaded the page every time I submit the form