iron-session is a secure, stateless, and cookie-based session library for JavaScript.

Clerk is a complete suite of embeddable UIs, flexible APIs, and admin dashboards to authenticate and manage your users.

Add authentication in 7 minutes 👉

The session data is stored in signed and encrypted cookies which are decoded by your server code in a stateless fashion (= no network involved). This is the same technique used by frameworks like Ruby On Rails.

Online demo and examples: https://get-iron-session.vercel.app 👀
Featured in the Next.js documentation ⭐️

• Table of Contents
• Installation
• Usage
• Examples
• Project status
• Session options
• API
  • getIronSession<T>(req, res, sessionOptions): Promise<IronSession<T>>
  • getIronSession<T>(cookieStore, sessionOptions): Promise<IronSession<T>>
  • session.save(): Promise<void>
  • session.destroy(): void
  • session.updateConfig(sessionOptions: SessionOptions): void
  • sealData(data: unknown, { password, ttl }): Promise<string>
  • unsealData<T>(seal: string, { password, ttl }): Promise<T>
• FAQ
  • Why use pure cookies for sessions?
  • How to invalidate sessions?
  • Can I use something else than cookies?
  • How is this different from JWT?
• Credits
• Good Reads

pnpm add iron-session

We have extensive examples here too: https://get-iron-session.vercel.app/.

To get a session, there's a single method to know: getIronSession.

// Next.js API Routes and Node.js/Express/Connect.
import { getIronSession } from 'iron-session';

export async function get(req, res) {
  const session = await getIronSession(req, res, { password: "...", cookieName: "..." });
  return session;
}

export async function post(req, res) {
  const session = await getIronSession(req, res, { password: "...", cookieName: "..." });
  session.username = "Alison";
  await session.save();
}

// Next.js Route Handlers (App Router)
import { cookies } from 'next/headers';
import { getIronSession } from 'iron-session';

export async function GET() {
  const session = await getIronSession(cookies(), { password: "...", cookieName: "..." });
  return session;
}

export async function POST() {
  const session = await getIronSession(cookies(), { password: "...", cookieName: "..." });
  session.username = "Alison";
  await session.save();
}

// Next.js Server Components and Server Actions (App Router)
import { cookies } from 'next/headers';
import { getIronSession } from 'iron-session';

async function getIronSessionData() {
  const session = await getIronSession(cookies(), { password: "...", cookieName: "..." });
  return session
}

async function Profile() {
  const session = await getIronSessionData();

  return <div>{session.username}</div>;
}

We have many different patterns and examples on the online demo, have a look: https://get-iron-session.vercel.app/.

✅ Production ready and maintained.

Two options are required: password and cookieName. Everything else is automatically computed and usually doesn't need to be changed.****

• password, required: Private key used to encrypt the cookie. It has to be at least 32 characters long. Use https://1password.com/password-generator/ to generate strong passwords. password can be either a string or an object with incrementing keys like this: {2: "...", 1: "..."} to allow for password rotation. iron-session will use the highest numbered key for new cookies.

• cookieName, required: Name of the cookie to be stored

• ttl, optional: In seconds. Default to the equivalent of 14 days. You can set this to 0 and iron-session will compute the maximum allowed value by cookies.

• cookieOptions, optional: Any option available from jshttp/cookie#serialize except for encode which is not a Set-Cookie Attribute. See Mozilla Set-Cookie Attributes and Chrome Cookie Fields. Default to:

  {
    httpOnly: true,
    secure: true, // set this to false in local (non-HTTPS) development
    sameSite: "lax",// https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite#lax
    maxAge: (ttl === 0 ? 2147483647 : ttl) - 60, // Expire cookie before the session expires.
    path: "/",
  }

type SessionData = {
  // Your data
}

const session = await getIronSession<SessionData>(req, res, sessionOptions);

type SessionData = {
  // Your data
}

const session = await getIronSession<SessionData>(cookies(), sessionOptions);

Saves the session. This is an asynchronous operation. It must be done and awaited before headers are sent to the client.

await session.save()

Destroys the session. This is a synchronous operation as it only removes the cookie. It must be done before headers are sent to the client.

session.destroy()

Updates the configuration of the session with new session options. You still need to call save() if you want them to be applied.

This is the underlying method and seal mechanism that powers iron-session. You can use it to seal any data you want and pass it around. One usecase are magic links: you generate a seal that contains a user id to login and send it to a route on your website (like /magic-login). Once received, you can safely decode the seal with unsealData and log the user in.

This is the opposite of sealData and allow you to decode a seal to get the original data back.

This makes your sessions stateless: since the data is passed around in cookies, you do not need any server or service to store session data.

More information can also be found on the Ruby On Rails website which uses the same technique.

Sessions cannot be instantly invalidated (or "disconnect this customer") as there is typically no state stored about sessions on the server by default. However, in most applications, the first step upon receiving an authenticated request is to validate the user and their permissions in the database. So, to easily disconnect customers (or invalidate sessions), you can add an `isBlocked`` state in the database and create a UI to block customers.

Then, every time a request is received that involves reading or altering sensitive data, make sure to check this flag.

Yes, we expose sealData and unsealData which are not tied to cookies. This way you can seal and unseal any object in your application and move seals around to login users.

Not so much:

• JWT is a standard, it stores metadata in the JWT token themselves to ensure communication between different systems is flawless.
• JWT tokens are not encrypted, the payload is visible by customers if they manage to inspect the seal. You would have to use JWE to achieve the same.
• @hapi/iron mechanism is not a standard, it's a way to sign and encrypt data into seals

Depending on your own needs and preferences, iron-session may or may not fit you.

• Eran Hammer and hapi.js contributors for creating the underlying cryptography library @hapi/iron.
• Divyansh Singh for reimplementing @hapi/iron as iron-webcrypto using standard web APIs.
• Hoang Vo for advice and guidance while building this module. Hoang built next-connect and next-session.
• All the contributors for making this project better.

• https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html
• https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html