Skip to content

Downstream OIDC authentication #556

Description

@shaneutt

What

Full OpenID Connect authentication flow for downstream clients connecting to Praxis. Validate client identity via OIDC discovery, token introspection, and refresh token handling.

Why

Enterprise deployments require centralized identity management for AI gateway access. OIDC is the standard for web-based SSO with providers like Auth0, Azure AD, Keycloak, and Okta. Without OIDC, operators must implement auth externally or rely on IP-based access control.

Goals

  • OIDC discovery via .well-known/openid-configuration
  • Token introspection endpoint support
  • Token exchange for upstream service calls
  • Refresh token handling
  • Configurable claims validation (issuer, audience, expiry)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions