next-auth gives 404 page not found on call back with chrome with Windows Accounts extension but works in incognito mode #4802
Unanswered
tinajohnck
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm new to next auth, followed the documentation on next-auth site(https://next-auth.js.org/providers/azure-ad) to create the authentication with Azure Active Directory. The SSO works perfect locally running from VS code with http://localhost:3000.
After deploying the next js application to the Azure Web Apps, in chrome and edge browser the next js application redirects to the microsoft sign in page and on call back from azure the server responds with a 404 error as below. but the same site works inconginto mode and as well as with firefox without giving any error. Any help will be greatly appreciated.
I have noticed that on chrome browser it has Windows Accounts extension and it looks to me like that's causing the problem when I access the application hosted in azure(but localhost works fine).Is there any setting in azure or next auth application that can solve this error?
This test.azureedge.net page can’t be foundNo webpage was found for the web address: https://test.azureedge.net/api/auth/callback/azure-ad?code=0.AVwACBLvBzxBXkuc3WTvMFdU8Am6QPVrIl9MvoD6fGF9wqhcAGk.AgABAAIBBAAS--DLA3VO7QrddgJg7WevrAgDs_wQA9P8UQCSOtQ1nvxrUHsYShINeBZU-ulViwaE8MidVklNGhfNHLdkAcTFYmC0j0Pyksb31t_Flk0BTDETAnd8PCjZZJJUNfNbe--PxrLt5v0FGBtt0OK-gJINH10rq_3heSvqWG1UJ87yCWbG1OvUX2qGb9BATYEyFC1gdhck-BRC9W6Hn5L18fj-5RBfPNwc6TGirsAUlx2jG4peMpTfcwq7xcuUwSWOL03uHZLvxzmGJcF-ABo0ZpoxFrCVs2A96XF0N1moliIl2Io5H1FlqfaYSR9zzOoP6e8B90vWAwNvPbFWNg2Cahs3-YJlIPYKX2k7sOSYlJd7elnbnkwISKmGf6_ttILro3D2d2EpteeU6dGUhBG59jfmlfrjJMiBJkOlWN8fGCC74hsR3QlUbYvGUm9L4eneNnhSg_IM_esADKmmMgppwzsTWM7HQRUmIW7XUMxtB0qjHAgbQKGIRSW0ckgcHhDP6vdhH7uotKiAodHmLRpWe0iSlyetoXhlzlegGUbfyQ47JOMH8_9WQvi1q86w_KdoGudWU7wdEwDDKSMgLGeb9h-nu7gTgooWrCH-0kp1JGmPInvFZLmWbgVe9oSvc7OOmz5Er22Pp-TDcijGCZv53kqpu9NWEXHoBdqy5DNxKJA4HnB05Hill47eWVy6QqgnooF4lZNhyxi_Gj2wBteyf8Py8QvqmE7cHKq9cdSkDlH4Ct2xJuJD4htSXm7bjJsKjMSuzwRTbU6L1tatx4OITtECKTplyyqoOGTGRn1WycwGTMFlAFnBRPLjppjh0eB506QEv9oC2ouEr6AW5qzYl5kIHrlhRPvjGtFHTOre5wOs2_BC_X8LyKpohh8-GCPGEGIJqVK3PGENBn5jIrQaZEojsWW7kBWaOCLmuS2B0Mce5KFTbjkKD&session_state=77c71622-8a37-4ba2-9d1f-2ccfc02ce75f
HTTP ERROR 404
Beta Was this translation helpful? Give feedback.
All reactions