What is Session vs Token Authentication?
Server sessions store state behind an opaque cookie, while tokens carry signed claims the client presents each request. BYOB apps typically delegate both models to managed auth rather than hand-rolling stores.
Related terms
JWT Claims
The signed JSON assertions inside a JSON Web Token, such as subject, expiry, issuer, and role. Services trust claims only after verifying signature, issuer, audience, and expiration together.
Refresh Token Rotation
The practice of issuing a fresh refresh token with every access-token renewal and invalidating the old one. Stolen tokens then expire quickly, and reuse of a spent token signals compromise.
Better Auth
Authentication with managed Google sign-in or email/password flows provisioned for generated apps. Auth pages (callbacks, sign-in) are private surfaces and stay noindexed like any other.
Cross-Site Request Forgery (CSRF)
An attack that tricks a logged-in browser into submitting unwanted state-changing requests to a trusted site. SameSite cookies, anti-CSRF tokens, and origin checks break the forgery chain.
SQL Injection
An attack that smuggles database commands through unsanitized input into application queries. Parameterized statements and least-privilege database roles keep hostile input as data, never executable code.
CSP Directives
The individual rules inside a Content Security Policy, such as script-src, object-src, and frame-ancestors. Each directive narrows one resource class, so auditing means reviewing directives one by one.