OpenID is an open standard and decentralized authentication protocol that allows users to be authenticated by certain co-operating sites using a third-party service.
Why this server?
Supports OpenID Connect (OIDC) proxy authentication for secure access control with configurable client credentials and provider integration
Why this server?
Used for authentication with Lulu's API through OpenID Connect protocol
Why this server?
Implements OAuth 2.1 authentication with OpenID Connect for secure token-based access, including JWT validation, token introspection, and session binding for enhanced security.
Why this server?
Provides authentication and identity management through OpenID as part of Medplum Auth services
Why this server?
Used as part of the authentication process for Google services, providing secure identity verification when connecting to Gmail and Google Calendar.
Why this server?
Supports OAuth authorization flows for MCP servers, allowing proxy to external OpenID providers with custom token validation.
Why this server?
Implements OpenID authentication flows as part of SMART-on-FHIR security standards for secure healthcare data access
Why this server?
Implements OpenID Connect authentication flow (via Auth0) to obtain user identity and API access tokens with specific scopes.
Why this server?
Implements OAuth2/OIDC authentication and authorization using Asgardeo as the identity provider, with JWT token validation via JWKS endpoints
