NextAuth.js (Auth.js) cookiesNone need consent
NextAuth.js (Auth.js) sets 6 cookies we know of. All of them are strictly necessary and exempt from consent.
Reviewed · Provider: NextAuth.js / Auth.js (Open Source), The website (Auth.js)
List of NextAuth.js (Auth.js) cookies
next-auth.session-tokenNecessaryNo consent needed30 daysEncrypted session token issued by NextAuth.js after successful authentication. Identifies the logged-in user.
next-auth.csrf-tokenNecessaryNo consent neededSessionCSRF token used to protect sign-in and sign-out form submissions in NextAuth.js.
next-auth.callback-urlNecessaryNo consent neededSessionStores the URL the user should be redirected to after a successful OAuth login.
authjs.session-tokenNecessaryNo consent needed30 daysHolds the Auth.js (NextAuth v5) session, so the visitor stays signed in.
authjs.csrf-tokenNecessaryNo consent neededSessionProtects Auth.js sign-in requests against cross-site request forgery.
authjs.callback-urlNecessaryNo consent neededSessionRemembers where to send the visitor after they sign in.
How to handle NextAuth.js (Auth.js) cookies
- 1No consent gate needed
NextAuth.js (Auth.js) cookies listed here are strictly necessary, so they can be set on the first visit.
- 2Still disclose them
List each cookie by name with its purpose, provider (NextAuth.js / Auth.js (Open Source), The website (Auth.js)) and lifetime in your cookie policy.
- 3Watch for add-ons
Extensions and marketing features of NextAuth.js (Auth.js) can add cookies that do need consent. Re-check after enabling one.
Other vendorsAnd the cookies they set
Does NextAuth.js (Auth.js) wait for consent on your site?Scan it in 2 minutes
Free scan · every cookie before consent, after Reject and after Accept