Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: remove outdated nested middleware info #5180 #5181

Merged
merged 2 commits into from Dec 31, 2022
Merged

fix: remove outdated nested middleware info #5180 #5181

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
32710ad
fix: remove outdated nested middleware info #5180
luiisca Aug 17, 2022
72c2c76
Merge branch 'v4' into patch-3
balazsorban44 Dec 31, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/docs/tutorials/securing-pages-and-api-routes.md
View file
Open in desktop
Expand Up @@ -48,8 +48,6 @@ With NextAuth.js 4.2.0 and Next.js 12, you can now protect your pages via the mi
export { default } from "next-auth/middleware"
```

Otherwise, if you only want to protect a subset of pages, you could put it in a subdirectory as well, for example in `/pages/admin/_middleware.js` would protect all pages under `/admin`.

For the time being, the `withAuth` middleware only supports `"jwt"` as [session strategy](https://next-auth.js.org/configuration/options#session).

More details can be found [here](https://next-auth.js.org/configuration/nextjs#middleware).
Expand Down