SUPERTOKENS

Configure Sso

Changed on

Configures SSO by creating a tenant if needed and updating third-party config

Self-service: the target is the tenant the caller addressed, never a request parameter, so this route was never the cross-tenant vector.

Uses get_request_tenant, not get_tenant: a SuperTokens tenant id is the host as-is, so a caller on pepsico.* must configure the pepsico SuperTokens tenant. Collapsing to the canonical pepsiaws-us-east wrote the config to a tenant that login never reads, because the frontend SDK sets getTenantId: getTenant (the subdomain) and SSO login calls /superauth/{subdomain}/authorisationurl. Identical for the 38 tenants whose host already is their canonical name. :return: ok status and optional message.

post/supertokens/configure/{provider}

Request

  • Base URL: https://api.myaltimate.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.myaltimate.com/supertokens/configure/{provider}
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

provider'okta' | 'active-directory' required

Providers customers may configure themselves via /configure/{provider}.

Deliberately narrower than ThirdPartySSO: this is the self-service allowlist, so a provider reachable through the support-assisted routes is not automatically exposed here.

Request body

client_idstring required
client_secretstring required
oidc_urlstring required

Response

Successful Response

unknown required

Changes