TEteaflask
authed

Register Sso Connection

Create the domain's one connection, born active: GoTrue registers the SAML provider from the IdP metadata and associates the domain, and the row lands already carrying the provider id. The Supabase call runs after every local precondition, with the session's transaction released around it (db/engine.py's standing rule: never hold a DbSession across a slow await) — the domain is re-read on the write side, so a claim revoked during the wire call still refuses.

post/api/v1/organizations/current/sso-connections

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/organizations/current/sso-connections
  • Auth
    none declared

Request body

email_domain_idstring uuid required
metadata_urlstring nullable
metadata_xmlstring nullable
entity_idstring nullable

Response

Successful Response

idstring uuid required
email_domain_idstring uuid required
status'pending' | 'active' | 'disabled' required

The connection lifecycle (the CHECK's mirror). pending awaits Supabase provider registration; active is a live federation anchored to a dns_verified domain; disabled withdraws federation — from active, or from a pending row abandoned before a provider ever existed — without erasing the row.

sso_requiredboolean required
metadata_urlstring nullable required
entity_idstring nullable required
created_atstring date-time required

Changes

No recorded changes to this operation across all 1 revision of this API.