Point an organization at its Zitadel IdP template (admin)
Create the connection, or re-point an existing one.
Idempotent by organization: there is at most one connection per organization, so a repeat call points the existing row rather than inserting a duplicate. The branch is chosen from the caller's scoped read, so a caller who cannot see the existing row falls to the create arm and is refused there -- by their own lack of the verb, or by the conflict on the organization slot.
Through the workflow rather than the connection service: naming a template id means reading that template back from Zitadel to derive the EntityID stored alongside it, which an entity service may not do. See :meth:~phoenix.services.workflows.users.sso_idp_template.SsoIdpTemplateWorkflow.point_at_template for what a connection pointed at a SAML template without one does.
Args: organization_id (int): The parent organization. payload (SsoTemplateRequest): Slug and template id. db (AsyncSession): Request-scoped session. context (ActiveContext): Resolved caller.
Returns: SsoConnectionResponse: The connection as it now stands.
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.