Test SSO Configuration
Validate an SSO configuration before pointing real users at it. For custom oidc providers this checks that the required auth_url, token_url, and userinfo_url endpoints are set; google and github configs use fixed, canonical endpoints and always validate. The outcome is persisted to the config's status (active on success, or error with last_error_message on failure).
Note that a passing test confirms the configuration is well-formed, not that a real login round-trip succeeded. For oidc, the id_token verification at login additionally relies on issuer and jwks_url (both required at save). SAML is not supported: a saml config saved earlier never signs anyone in; replace it with an oidc one.
Recommended after any change to create / update — especially after rotating credentials or changing the provider endpoints.
Account-scoped: operates on the caller's active account. Permission-gated: requires the settings:update permission (the test mutates the config status). Plan-gated: requires the sso entitlement.
Path parameters
uuid, from /sso/config.Deprecated: the legacy integer id is still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuid.
Request body
None — empty body or {}.
Response (200 OK)
true if the configuration validated successfully.success: true.Errors
integer_id_unsupported).settings:update permission, or the account plan doesn't include the sso entitlement.