Single Sign-On
Other OpenID Connect ProvidersEnterprise
Connecting any identity provider that supports OpenID Connect.
Multi-Router connects to any identity provider that supports OpenID Connect sign-in with the authorization code flow, such as Keycloak, Auth0 or Authentik, as well as the providers with their own pages. Choose Other / Generic as the Identity provider, and create an app in the identity provider with the settings below.
Requirements
The identity provider app needs these settings:
| Setting | Value |
|---|---|
| Application type | A web application, also called a confidential client, with a client secret. |
| Grant type | Authorization code, with PKCE allowed. |
| Redirect URI | https://dashboard.multi-router.ai/sso/callback |
| Client authentication | Client secret sent in the request body, often called client_secret_post. |
| Scopes | openid, email and profile. |
| ID token claims | email, with email_verified true or absent. |
| Signing algorithm | RS256, RS384, RS512, PS256, PS384, PS512, ES256 or ES384. |
| Issuer | A public https address that serves /.well-known/openid-configuration. |
Finding the issuer
The issuer is the issuer value in the provider's discovery document, at the issuer address followed by /.well-known/openid-configuration. Enter it exactly as the document shows it, including any trailing slash. Common forms:
| Provider | Issuer form |
|---|---|
| Keycloak | https://sso.example.com/realms/example |
| Auth0 | https://example.us.auth0.com/ |
| Authentik | https://auth.example.com/application/o/multi-router/ |
Every person who signs in has an email in the company's email domain, the domain set on the SSO connection, and apps that sign tokens with HS256 are switched to RS256.
Connecting it
Choose Other / Generic on the Single Sign-On (SSO) page, enter the email domain, issuer, client ID and client secret, and finish the steps on Setting Up SSO. Test connection checks the discovery document and signing keys, and a sign-in from a private browser window checks the rest.