Request
/.well-known/openid-configuration, such as https://acme.eu.auth0.com/. A bare domain (acme.eu.auth0.com) also works. It must use https:// and reach a public address. Hyperping saves the issuer the discovery document publishes, so the response can spell it differently from the request.["acme.com"]: a visitor's email must be at one of them. Empty lets in any account the identity provider signs in for the application. At most 100 domains, stored as sent. Default: []oidc is accepted. SAML connections are created in the dashboard. Default: oidcBefore you call it
Create a web application with a client secret in your identity provider, and register https://api.hyperping.io/v1/auth/sso/oidc/callback as an allowed callback URL (https://api.eu.hyperping.io/v1/auth/sso/oidc/callback for EU accounts). The response returns this URL as redirect_uri. The status page SSO guide and the Auth0 guide walk through the provider side.
What Hyperping checks
Before anything is saved, Hyperping fetches the discovery document of the issuer, then asks the identity provider whether it accepts the client ID and secret. If either check fails, the request fails with 400: the body names the failed check in code and lists every check in checks. When the identity provider's answer does not say either way, the connection is saved: run Test connection on its card in the dashboard to try a real sign-in.
Billing
The connection is billed like one created in the dashboard, from the moment it is created: $49 per month (€49 on EUR billing), or included on plans that include SSO connections. The project's owner needs a payment method on file. See pricing.
Response
Returns 201 with the new connection object. Set its uuid as authentication.sso_connection_uuid when you create or update a status page.
Errors
name is required or allowed_domains: "acme" is not a domain (example: acme.com)code says why, for example discovery_not_found, insecure_url, unreachable, client_refused or client_grant_not_allowedprovider is not oidc