Set Session Cookie missing from azure-ad callback in production #10613
Labels
bug
Something isn't working
invalid reproduction
The issue did not have a detectable valid reproduction URL
providers
triage
Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime.
Provider type
Azure Active Directory
Environment
System:
OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-1360P
Memory: 13.30 GB / 15.46 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
npmPackages:
@auth/prisma-adapter: ^1.4.0 => 1.6.0
next: 14.2.1 => 14.2.1
next-auth: 4.24.7 => 4.24.7
react: 18.2.0 => 18.2.0
Reproduction URL
N/A
Describe the issue
When using the Azure AD provider, I have had something weird occur that when I have pushed the new version of a code set to Vercel, the sign-in functionality is no longer working. The auth options have not changed and when hooked up to the db locally the signin flows as expected but in vercel deployments the set session cookie from the azure-ad callback is not present.
The session is created in the DB however.
How to reproduce
I am unable to reproduce this locally, or in another project.
Expected behavior
I would expect to sign in as expected
The text was updated successfully, but these errors were encountered: