Start a federated-login configuration test (owner)
Hand back a real login ceremony to run against the customer's own IdP.
The safety net under PUT .../sso/policy: every interlock there proves the configuration is coherent, and none of them proves the customer's IdP answers. An owner who turns on require_sso against a connection that does not work locks out an organization whose members hold no password.
POST because it creates an intent in Zitadel, and no body because the only input is the connection, which the path already names. Answers 400 for a connection no admin has pointed anywhere, and 503 when this deployment configured no return URLs.
Args: organization_id (int): The parent organization. db (AsyncSession): Request-scoped session. context (ActiveContext): Resolved caller.
Returns: SsoTestStartResponse: A redirect URL or a form to POST, depending on the provider's binding.
Request
- Base URLhttps://api.ethiack.com (the document declares no server; this is the origin it was published from)
- Authnone declared
Path parameters
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.