Single Sign-on
SSO-Verbindungen auflisten
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.
AuthentifizierungBearer <token>
Bearer-Token, erhalten über den Login-Endpunkt (POST /rest/login).
Ort: header
Response-Body
application/json
application/json
curl -X GET "https://example.com/sso/connections"{ "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-Token eintauschen POST
Unknown, expired, already redeemed and wrong-verifier codes all answer with the same 401 — the endpoint must not confirm that a code exists.
SSO-Verbindung konfigurieren PUT
Idempotent upsert — always 200, also on the first write, so the admin screen has one status code to handle.