v5
latestOpenAPI 3.1.02026-08-081,0211,3082.1 MBSUPERTOKENS
Configure Sso
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 Okta 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}
Path parameters
provider'okta' required
Request body
Response
Successful Response
{"stackTrail":"paths:/supertokens/configure/{provider}:post:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}