Authentication
Verify identity at request boundaries and keep provider sessions separate from application permissions.
Verify identity before private work
Auth turns a provider-verified session into a small immutable identity. The request guard also checks trusted origins for unsafe cookie-authenticated requests. It does not implement passwords, organizations or a universal authorization engine.
- Verify requests and sessions before parsing bodies or allocating work.
- Connect Better Auth without replacing its native session lifecycle.
- Authentication forms for application-owned Octane sign-in and recovery UI.
Identity is not permission
After authentication, the application still checks membership, resource ownership and operation-level authorization. A user ID in a header, URL, cache key or thread ID grants no access.
Tool policies and human decisions have a different purpose; see Policies, approvals and audit.