Patch SSO
Updates only the fields present in the payload. Fields left out keep their currently stored value. The resulting configuration is validated as a whole, so a partial update that leaves the configuration incomplete or invalid is rejected.
Session authentication token.
Whether SSO authentication is enabled for the pod.
trueEntity id of the identity provider.
https://idp.example.com/metadataUrl the user is redirected to in order to authenticate.
https://idp.example.com/sso/samlPEM encoded certificate used to verify the identity provider's assertions.
-----BEGIN CERTIFICATE-----MIIH/TC...p9DBiB/-----END CERTIFICATE-----Assertion consumer service url the identity provider posts back to. Derived from the pod's base url when the configuration has not been created yet.
https://yourpodURL.symphony.com/login/sso/acsEntity id Symphony identifies itself with. Derived from the pod's base url when the configuration has not been created yet.
https://yourpodURL.symphony.comWhether to force users to re-authenticate with the Identity Provider during SSO, even if they have an existing active session.
Success
TEXTPossible values: SuccessClient error, see response body for further details.
Unauthorized: Session tokens invalid.
Forbidden: Caller lacks necessary entitlement.
Server error, see response body for further details.
PATCH /pod/v1/admin/sso/configuration HTTP/1.1
Host: yourpodURL.symphony.com
sessionToken: text
Content-Type: application/json
Accept: */*
Content-Length: 352
{
"ssoEnabled": true,
"idpEntityId": "https://idp.example.com/metadata",
"idpSsoEndpoint": "https://idp.example.com/sso/saml",
"idpSigningCertificate": "-----BEGIN CERTIFICATE-----MIIH/TC...p9DBiB/-----END CERTIFICATE-----",
"symphonyAcsUrl": "https://yourpodURL.symphony.com/login/sso/acs",
"symphonyEntityId": "https://yourpodURL.symphony.com",
"forceAuthn": true
}{
"format": "TEXT",
"message": "Success"
}Last updated
Was this helpful?