SSO-Verbindung konfigurieren
Idempotent upsert — always 200, also on the first write, so the admin screen has one status code to handle.
Bearer-Token, erhalten über den Login-Endpunkt (POST /rest/login).
Ort: header
Pfadparameter
Request-Body
application/json
TypeScript-Definitionen
TypeScript-Typ für request body.
Validation of one provider's connection row.
The rules differ per provider on purpose: Entra cannot federate without the
directory id, Google has no directory id at all. The fields of the other
provider are prohibited rather than merely ignored, so a client that
posts the wrong shape learns about it instead of silently losing a value.
Response-Body
application/json
application/json
application/json
curl -X PUT "https://example.com/sso/connections/string" \ -H "Content-Type: application/json" \ -d '{}'{ "data": { "id": "string", "provider": "string", "configured": true, "entra_tenant_id": "string", "allowed_domains": [ "string" ], "enabled": true, "allow_guest_accounts": true, "has_custom_app": true, "usable": true, "requires_admin_consent": true, "consent_granted_at": "string", "last_login_at": "string", "last_error": "string", "redirect_uri": "string", "updated_at": "string" }}SSO-Verbindungen auflisten GET
Every supported provider, configured or not — an unconfigured one comes back as a disabled placeholder so the admin screen has one list to bind against and does not have to know the provider catalogue itself.
SSO-Verbindung löschen DELETE
Removes one provider's configuration entirely; the audit trail in sso_login_attempts is deliberately kept.