Archestra LLM Gateway v1.2.33 Expands Authentication Methods for Enterprise and Developer Use Cases
Key Takeaways
- ▸Five authentication methods now supported: direct provider keys, virtual API keys, OAuth client credentials, user OAuth, and JWKS
- ▸Virtual API keys serve as the default solution for generic LLM clients and individual developers
- ▸OAuth client credentials enable secure backend service integration with token-based authentication
Summary
Archestra has released version 1.2.33 of its LLM Gateway with comprehensive authentication support spanning five distinct methods. The update addresses authentication complexity in LLM proxy deployments by offering direct provider keys for simple integrations, virtual API keys for generic clients, OAuth client credentials for backend services, user OAuth for role-based access, and identity provider JWKS for enterprise environments. Each method maintains Archestra's core policy enforcement, logging, and observability features while enabling different security and credential management patterns. The authentication flexibility allows teams to choose the method best suited to their architecture—from local development to production applications.
- User OAuth allows per-user provider key management across personal, team, and organization scopes
- All methods integrate with Archestra's Model Router and maintain proxy-level policy, logging, and observability
