Litestar Auth and Guards

Use this skill for authentication boundaries, authorization checks, guard composition, and user context.

Code Style Rules

• Put auth and permission checks in Guards or middleware, not handler bodies.
• Prefer Controller-level guards when a whole domain shares a policy.
• Raise Litestar HTTP exceptions or domain exceptions consistently.
• Keep tenant isolation explicit in guard logic and service filters.
• Let authentication middleware populate connection.user and connection.auth; use guards for authorization.

Quick Reference

• Guard patterns: guards.md
• Middleware user loading: litestar-middleware
• Realtime auth: litestar-realtime