Auth for Next.jss
Auth in Next.js covers proving who a user is and deciding what they may do. Authentication usually means sessions in secure cookies or signed tokens, often through a library such as Auth.js. Authorisation then checks roles or ownership on the server, in route handlers, Server Actions and data access code.
Stage: Full-stack Features · Part of the Next.js roadmap · Last reviewed 19 November 2026
What to learn in Auth
- Set up a login flow that stores a session in an httpOnly cookie
- Read the current session inside a Server Component
- Protect routes with middleware as a first, coarse check
- Check permissions inside Server Actions and data access functions
- Explain why client-side hiding of buttons is not real authorisation
Auth interview questions
Why is checking auth only in Next.js middleware not enough?
Middleware is a convenient early gate, but it can be skipped by misconfigured matchers and does not see every data path. Real checks belong next to the data, in Server Actions, route handlers and queries, so each operation verifies the user itself.
How do authentication and authorisation map to middleware and server checks in Next.js?
Authentication establishes identity, for example by checking a password or an OAuth login. Authorisation decides what that identity may access, such as editing only their own posts or viewing admin pages. A logged-in user can still be refused by an authorisation check. Check permissions again in server code.
Where Auth fits in the Next.js roadmap
Auth belongs to the Full-stack Features stage (intermediate level), which takes about 16 hours. Auth and data stores.
Other units in this stage
Back to the full Next.js roadmap