Third-party integrations are nested throughout the relevant use case sections. The following table displays links to the third-party use cases:
Provision data to and from Identity Cloud and PingDirectory.
Identity Cloud serves as the IDP for Okta using OIDC.
Validate by navigating to Okta, being redirected to Identity Cloud and logging in, and then being redirected back to Okta logged in.
Identity Cloud serves as the IDP for Salesforce using SAML.
Validate by logging into the Identity Cloud End User UI to SSO into Salesforce.
Configure social authentication by letting Microsoft Entra ID serve as the IDP to Identity Cloud using OIDC.
Validate by authenticating with Microsoft Entra ID and automatically be signed in to the Identity Cloud End User UI.
Connect to Microsoft Entra ID in a journey to capture an end user’s password, after successful authentication, to store in Identity Cloud.
Validate by authenticating with Microsoft Entra ID in a PTA journey for Identity Cloud to capture the password. Then, log into the Identity Cloud End User UI with the default login journey to show that Identity Cloud successfully stored the password.
Configure Microsoft Entra ID to serve as an authoritative application to provision users into Identity Cloud.
Validate by reconciling a test user from Microsoft Entra ID to Identity Cloud.
Provision users from an on-prem data source, AD, using a remote connector server (RCS).
Validate by reconciling a test user from AD to Identity Cloud.