Overview

Zelt provides a flexible authentication system that separates authentication (who is the user?) from authorization (what can they do?).

Authentication vs Authorization

Concept	Question	Zelt API
Authentication	Who is the user?	setUser(), currentUser()
Authorization	What can they do?	@Authorized(), currentRoles()

Authentication happens first (typically in middleware), then authorization checks run on protected routes.

Choose Your Strategy

Zelt supports multiple authentication strategies. Pick the one that fits your architecture:

Strategy	Best For	Package
JWT	SPAs, Mobile apps, APIs	@zeltjs/auth-jwt
Sessions	Server-rendered apps, Traditional web apps	@zeltjs/auth-session
Custom	API keys, OAuth, or any other method	Built-in primitives

Decision Guide

Authentication Flow

Quick Start

1. Install a package (or use built-in primitives)

# For JWT authentication
pnpm add @zeltjs/auth-jwt

# For session authentication
pnpm add @zeltjs/auth-session @zeltjs/kv

2. Register middleware

const app = createApp([http({
    controllers: [UserController],
    middlewares: [JwtMiddleware],
  })], { configs: [JwtConfig] });

3. Protect routes

@Controller('/dashboard')
class DashboardController {
  @Authorized()
  @Get('/')
  index() {
    const user = currentUser();
    return { message: `Hello, ${user?.name}` };
  }
}

Next Steps

• User Context — How to type and access the authenticated user
• JWT Authentication — Stateless token-based authentication
• Session Authentication — Cookie-based session management
• Custom Authentication — Build your own authentication middleware