Set up federated login from your own IdP (owner)
Mint the owner's own IdP template in one call -- no admin, no slug to pick.
The self-service counterpart to the admin's two-step (PUT .../sso/template then POST .../sso/idp): :meth:OwnerSsoProvisioningWorkflow.establish derives the slug from the organization name, creates the connection disabled and unverified, and mints the template. SSO is a paid feature, so an organization whose plan lacks it is refused (402) before any Zitadel call. First-time setup only -- an organization already pointed at a template is refused (409); changing a live one is PUT .../sso/idp/self.
For SAML the response is part of the deliverable -- the ACS, metadata, certificate and SLO URLs unique to this template, which the customer configures their IdP against.
Args: organization_id (int): The parent organization. payload (SsoIdpRequest): Provider configuration, discriminated on protocol. db (AsyncSession): Request-scoped session. context (ActiveContext): Resolved caller.
Returns: IdpTemplateResponse: The template id and, for SAML, the customer's URLs.
Request
- Base URLhttps://api.ethiack.com (the document declares no server; this is the origin it was published from)
- Authnone declared
Path parameters
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.