apollos-ai

The system maps Entra ID identities to LiteLLM teams and API keys to enable secure access to LLM proxies. It automates user enrollment by applying provisioning, key lifecycle, and usage tracking across portal, CLI, and API interfaces.

Managing LLM proxy access requires a Microsoft Entra ID app registration with User.Read and GroupMember.Read.All permissions. These permissions allow the system to read user profiles and group memberships for mapping identities to LiteLLM teams.

Entra ID group memberships are used to provision users into corresponding LiteLLM teams. When users sign in through the portal, their group memberships determine their team assignments and generate the appropriate initial API keys for LLM proxy access.

Yes, setting up self-service LLM access requires Python 3.12, PostgreSQL 18, and a running LiteLLM proxy. These components provide the runtime environment and data storage needed to manage API key lifecycles and track usage.

Yes, the self-service portal supports managing LiteLLM API keys including creating, rotating, and revoking them. Users can also view their usage statistics and model access permissions through the same interface.

Admin endpoints provide capabilities for auditing LLM API usage, deprovisioning users, and monitoring system health. These endpoints allow administrators to oversee the entire key lifecycle and maintain secure access controls across the LLM proxy.