srizan/archived-next-auth
1
0
Fork 0
mirror of https://github.com/SrIzan10/next-auth.git synced 2026-05-01 10:55:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update client max age documentation

Browse Source
This commit is contained in:
Iain Collins
2020-06-23 20:54:55 +01:00
parent fbbe516b9a
commit b024f89ba8
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
www/docs/configuration/options.md
View File

@@ -411,14 +411,14 @@ Changing the cookie options may introduce security flaws into your application a
By default the NextAuth.js client will use whatever cached session object it has and will not not re-check the current session if using the `useSession()` hook.
You can change this behaviour and force it to periodically sync the session state by setting a `NEXTAUTH_CLIENT_MAXAGE` environment variable.
You can change this behaviour and force the client to periodically sync the session state by setting the `maxAge` option in the client in `pages/_app.js`:
```js title="next.config.js"
module.exports = {
env: {
NEXTAUTH_CLIENT_MAXAGE: 60, // Will re-check session every 60 seconds
},
}
```js title="pages/_app.js"
import { config } from 'next-auth/client'
config({
site: process.env.SITE, // e.g. 'http://localhost:3000'
maxAge: 60, // Will re-check session every 60 seconds
})
```
If set to `0` (the default) sessions are not re-checked automatically, only when a new window or tab is opened or when `getSession()` is called.