Regarding sign-in page..

[Prathamesh557]

When we enter details on sign-in page , and hit submit , it is not redirecting to dashboard..

I request genuinely Hitesh Sir to please upload the repo of fully working project as this is having alot of issues..

[AbhinavSharma486]

When we enter details on sign-in page , and hit submit , it is not redirecting to dashboard..

I request genuinely Hitesh Sir to please upload the repo of fully working project as this is having alot of issues..

same issue i also facing

[anshukantjha]

configure your middleware as per documentation
`import NextAuth from "next-auth"

export const { auth, handlers } = NextAuth({
callbacks: {
authorized: async ({ auth }) => {
// Logged in users are authenticated, otherwise redirect to login page
return !!auth
},
},
})`
Link provided:
https://authjs.dev/getting-started/session-management/protecting#nextjs-middleware
or you can use prop redirectTo there also

[anshukantjha]

Btw i have issue why result gives redirecturl only it should be a object upon console log
Inside submitHandler as
const submitHandler = async (data: z.infer<typeof signInSchema>) => { try { const result = await postSignIn(data); console.log(result); if (result?.error) { if (result.error === "CredentialsSignin") { toast({

output of result is not expected and that might be also your issue @AbhinavSharma486 @Prathamesh557 cause result object has no url so if (result?.url) { router.replace("/dashboard"); }
these snippet is not excecuted

[Haiderghadi]

did this issue got solved ?? i am facing the same problem, can anyone help?

[KunalNasa]

did this issue got solved ?? i am facing the same problem, can anyone help?

I have created a pull request for it. So the problem is that the token is NULL in middleware.ts (You can check by console.log(token)) due to which we are redirecting to sig-in route even when the user is logged in. To resolve this issue you have to provide NEXT_AUTH_TOKEN to your getToken() method.
const token = await getToken({ req: request, secret: process.env.NEXT_AUTH_SECRET });
This will resolve this issue

[Haiderghadi]

🙏🙏👍

…

On Thu, 19 Sep 2024 at 4:42 PM, Kunal Nasa ***@***.***> wrote: did this issue got solved ?? i am facing the same problem, can anyone help? I have created a pull request for it. So the problem is that the token is NULL in middleware.ts (You can check by console.log(token)) due to which we are redirecting to sig-in route even when the user is logged in. To resolve this issue you have to provide NEXT_AUTH_TOKEN to your getToken() method. const token = await getToken({ req: request, secret: process.env.NEXT_AUTH_SECRET }); This will resolve this issue — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7ENXX2LXVUQ2R6GAUIP5CLZXKWTDAVCNFSM6AAAAABLOLCTV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRQGY4TMMJWGY> . You are receiving this because you commented.Message ID: ***@***.***>