An identity provider lets you configure a generic OpenID Connect (OIDC) authentication service (such as Active Directory Federation Services (ADFS), Okta, or Keycloak) for a PBX, so your users can sign in to Cockpit with their existing corporate account through Single Sign-On. For Microsoft Entra ID, use the dedicated Microsoft SSO type instead of configuring an identity provider here.
Overview
Identity providers use OpenID Connect (OIDC) to delegate authentication to services such as Active Directory Federation Services (ADFS), Okta, or Keycloak. Once configured, users on the associated PBX can authenticate through their existing organization account instead of a separate password. Each PBX has a single identity provider. (Microsoft Entra ID has its own dedicated Microsoft SSO type, so it does not need an identity provider configured here.)
What it does
Cockpit acts as an OIDC relying party. When a user chooses SSO login, Cockpit redirects them to the provider's authorization endpoint, exchanges the resulting code for tokens, and retrieves the user profile from the userinfo endpoint. Pasting the discovery URL auto-fills these endpoints from the provider's well-known configuration document, so you rarely need to enter them by hand.
See also
- PBX instances - each identity provider is scoped to a single PBX.