auth-architecture

Authenticate and authorize API requests with JWTs, API keys, and RBAC.

104|19|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/majiayu000/litellm-rs --skill auth-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-architecture
Source: https://github.com/majiayu000/litellm-rs/tree/main/.claude/skills/auth-architecture
Command: npx skills add https://github.com/majiayu000/litellm-rs --skill auth-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LiteLLM-RS Authentication Architecture provides a secure, scalable framework for authenticating and authorizing API requests using JWTs, API keys, and RBAC, with built-in rate limiting and a robust middleware pipeline.

Core Features & Use Cases

  • Multi-method authentication: JWTs and API keys with centralized validation
  • RBAC-based authorization: configurable roles and permission checks
  • Rate limiting: lock-free per-user quotas to protect APIs
  • Middleware orchestration: pluggable pipeline for auth, logging, and access control
  • Secure credential management: key rotation, auditing, and safe storage

Quick Start

Start by enabling authentication in your gateway config, generate an API key or JWT for a test user, and wire the auth middleware in your route definitions to enforce permissions.

Frequently Asked Questions about auth-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate API requests using JWTs and API keys in a microservice gateway?

Authenticating API requests using JWTs and API keys requires centralized validation within a middleware pipeline. This framework provides multi-method authentication, validating tokens and keys across microservice boundaries to ensure secure, auditable access control.

How does RBAC authorization work with per-user rate limiting for APIs?

RBAC authorization with per-user rate limiting enforces configurable roles and permissions alongside lock-free user quotas. This combination protects APIs from abuse by verifying user roles and applying strict request limits before processing authorized microservice traffic.

What is the best way to implement secure credential management and key rotation for microservices?

Secure credential management and key rotation for microservices require centralized key generation, safe storage, and auditing. This framework implements these features within its middleware pipeline, ensuring credentials are rotated and validated securely across services.

Can I use a pluggable middleware pipeline for layered security across microservice boundaries?

Using a pluggable middleware pipeline for layered security across microservice boundaries is fully supported. The framework orchestrates authentication, logging, and access control sequentially, enforcing RBAC checks and rate limits at gateway endpoints.

When do I need multi-method authentication and authorization for my API gateway?

Multi-method authentication and authorization are needed when an API gateway requires layered security, supporting both JWTs and API keys. It is essential for microservice architectures demanding per-user rate limiting, RBAC permissions, and auditable access controls.