Skip to content

Commit

Permalink
Remove reference to nested middlware in docs
Browse files Browse the repository at this point in the history
  • Loading branch information
stphnnnn committed Sep 16, 2022
1 parent ba55f06 commit 8504f43
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions docs/docs/tutorials/securing-pages-and-api-routes.md
Expand Up @@ -42,13 +42,19 @@ export default function Page() {

### Next.js (Middleware)

With NextAuth.js 4.2.0 and Next.js 12, you can now protect your pages via the middleware pattern more easily. If you would like to protect all pages, you can create a `_middleware.js` file in your root `pages` directory which looks like this.
With NextAuth.js 4.2.0 and Next.js 12, you can now protect your pages via the middleware pattern more easily. If you would like to protect all pages, you can create a `_middleware.js` file in your root `pages` directory which looks like this:

```js title="/middleware.js"
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`.
If you only want to secure certain pages, export a `config` object with a `matcher`:

```js
export { default } from "next-auth/middleware"

export const config = { matcher: ["/dashboard"] }
```

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

Expand Down

0 comments on commit 8504f43

Please sign in to comment.