A session plugin for fastify. Requires the fastify-cookie plugin.
NOTE: This is the continuation of fastify-session which is unmaintained by now. All work credit till e201f7
commit goes to SerayaEryn and contributors.
npm i @fastify/session
const fastify = require('fastify');
const fastifySession = require('@fastify/session');
const fastifyCookie = require('fastify-cookie');
const app = fastify();
app.register(fastifyCookie);
app.register(fastifySession, {secret: 'a secret with minimum length of 32 characters'});
Store data in the session by adding it to the session
decorator at the request
:
app.register(fastifySession, {secret: 'a secret with minimum length of 32 characters'});
app.addHook('preHandler', (request, reply, next) => {
request.session.user = {name: 'max'};
next();
})
NOTE: For all unencrypted (HTTP) connections, you need to set the secure
cookie option to false
. See below for all cookie options and their details.
The session
object has methods that allow you to get, save, reload and delete sessions.
app.register(fastifySession, {secret: 'a secret with minimum length of 32 characters'});
app.addHook('preHandler', (request, reply, next) => {
request.session.destroy(next);
})
The session plugin accepts the following options. It decorates the request with the sessionStore
and a session
object. The session data is stored server-side using the configured session store.
The secret used to sign the cookie. Must be an array of strings or a string with a length of 32 or greater or a custom signer.
If an array, the first secret is used to sign new cookies and is the first to be checked for incoming cookies. Further secrets in the array are used to check incoming cookies in the order specified.
For a custom signer see the documentation of @fastify/cookie
Note that the rest of the application may manipulate the array during its life cycle. This can be done by storing the array in a separate variable that is later used with mutating methods like unshift(), pop(), splice(), etc. This can be used to rotate the signing secret at regular intervals. A secret should remain somewhere in the array as long as there are active sessions with cookies signed by it. Secrets management is left up to the rest of the application.
The name of the session cookie. Defaults to sessionId
.
Prefix for the value of the cookie. This is useful for compatibility with express-session
, which prefixes all cookies with "s:"
. Defaults to ""
.
The options object is used to generate the Set-Cookie
header of the session cookie. May have the following properties:
path
- ThePath
attribute. Defaults to/
(the root path).maxAge
- Anumber
in milliseconds that specifies theExpires
attribute by adding the specified milliseconds to the current date. If bothexpires
andmaxAge
are set, thenmaxAge
is used.rolling
- Forces the session identifier cookie to be set on every response. The expiration is reset to the original maxAge - effectively resetting the cookie lifetime. This is typically used in conjuction with short, non-session-length maxAge values to provide a quick expiration of the session data with reduced potential of session expiration occurring during ongoing server interactions. Defaults to true.httpOnly
- Theboolean
value of theHttpOnly
attribute. Defaults to true.secure
- Theboolean
value of theSecure
attribute. Set this option to false when communicating over an unencrypted (HTTP) connection. Value can be set toauto
; in this case, theSecure
attribute will be set to false for an HTTP request. In the case of HTTPS, it will be set to true. Defaults to true.expires
- The expirationdate
used for theExpires
attribute. If bothexpires
andmaxAge
are set, thenmaxAge
is used.sameSite
- Theboolean
orstring
of theSameSite
attribute. UsingSecure
mode withauto
attribute will change the behavior of theSameSite
attribute inhttp
mode. TheSameSite
attribute will automatically be set toLax
with anhttp
request. See this link.domain
- TheDomain
attribute.
A session store. Needs the following methods:
- set(sessionId, session, callback)
- get(sessionId, callback)
- destroy(sessionId, callback)
Compatible to stores from express-session.
Defaults to a simple in-memory store.
Note: The default store should not be used in a production environment because it will leak memory.
Save sessions to the store, even when they are new and not modified— defaults to true
.
Setting this to false
can save storage space and comply with the EU cookie law.
Function used to generate new session IDs. Custom implementation example:
const uid = require('uid-safe').sync
idGenerator: (request) => {
if (request.session.returningVisitor) return `returningVisitor-${uid(24)}`
else return uid(24)
}
Allows to access or modify the session data.
Allows to destroy the session in the store. If you do not pass a callback, a Promise will be returned.
Updates the expires
property of the session's cookie.
Regenerates the session by generating a new sessionId
and persist it to the store. If you do not pass a callback, a Promise will be returned.
fastify.get('/regenerate', (request, reply, done) => {
request.session.regenerate(error => {
if (error) {
done(error);
return;
}
reply.send(request.session.sessionId);
});
});
Reloads the session data from the store and re-populates the request.session
object. If you do not pass a callback, a Promise will be returned.
Save the session back to the store, replacing the contents on the store with the contents in memory. If you do not pass a callback, a Promise will be returned.
Gets a value from the session
Sets a value in the session
This plugin also decorates the fastify instance with decryptSession
in case you want to decrypt the session manually.
const { sessionId } = fastify.parseCookie(cookieHeader);
const request = {}
fastify.decryptSession(sessionId, request, () => {
// request.session should be available here
})
// or decrypt with custom cookie options:
fastify.decryptSession(sessionId, request, { maxAge: 86400 }, () => {
// ...
})
This plugin supports typescript, and you can extend fastify module to add your custom session type.
declare module "fastify" {
interface Session {
user_id: string
other_key: your_prefer_type
id?: number
}
}
While this plugin can be used with express-session compatible stores, the type definitions of some stores might be tied to express-session, which means that casting to any
might be required. For example:
import fastifySession from '@fastify/session'
import fastify from 'fastify'
import Redis from 'ioredis'
import connectRedis from 'connect-redis'
const RedisStore = connectRedis(fastifySession as any)
const redisClient = new Redis(redisConfig)
const server = fastify()
server.register(fastifySession, {
store: new RedisStore({
client: redisClient,
// ... other options
}) as any,
// ... other options
})