Third-party integrations

PingOne Advanced Identity Cloud third-party integrations are included throughout the relevant use case sections. The following table provides links to the third-party use cases:

Use case	Description
Provision data between Advanced Identity Cloud and PingDirectory	Provision data to and from Advanced Identity Cloud and PingDirectory. Validate by provisioning a user from a PingDirectory server to Advanced Identity Cloud and provisioning a user from Advanced Identity Cloud to a PingDirectory server.
Okta as RP (OIDC)	Advanced Identity Cloud serves as the IdP for Okta using OIDC. Validate by navigating to Okta, being redirected to Advanced Identity Cloud and signing on, and then being redirected back to Okta signed in.
Salesforce as SP (SAML)	Advanced Identity Cloud serves as the IdP for Salesforce using SAML. Validate by signing on to the Advanced Identity Cloud end-user UI to SSO into Salesforce.
Microsoft Entra ID (Azure AD) as OpenID provider	Configure social authentication by letting Microsoft Entra ID (formerly Azure AD) serve as the IdP to Advanced Identity Cloud using OIDC. Validate by authenticating with Microsoft Entra ID and automatically be signed on to the Advanced Identity Cloud end-user UI.
Ping Identity as external authentication method for Microsoft Entra ID (Azure AD)	Configure Advanced Identity Cloud as an external authentication method for Microsoft Entra ID (formerly Azure AD). Validate by using Advanced Identity Cloud as a second authentication factor for Microsoft Entra ID.
Pass-through auth (PTA) with Microsoft Entra ID (Azure AD)	Connect to Microsoft Entra ID (formerly Azure AD) in a journey to capture an end user’s password, after successful authentication, to store in Advanced Identity Cloud. Validate by authenticating with Microsoft Entra ID in a PTA journey for Advanced Identity Cloud to capture the password. Then, sign on to the Advanced Identity Cloud end-user UI with the default login journey to show that Advanced Identity Cloud successfully stored the password.
Provision data from Active Directory (AD) using RCS	Provision users from an on-premises data source, AD, using a remote connector server (RCS). Validate from AD by using Advanced Identity Cloud.

Use case

Description

Provision data between Advanced Identity Cloud and PingDirectory

Provision data to and from Advanced Identity Cloud and PingDirectory.

Validate by provisioning a user from a PingDirectory server to Advanced Identity Cloud and provisioning a user from Advanced Identity Cloud to a PingDirectory server.

Okta as RP (OIDC)

Advanced Identity Cloud serves as the IdP for Okta using OIDC.

Validate by navigating to Okta, being redirected to Advanced Identity Cloud and signing on, and then being redirected back to Okta signed in.

Salesforce as SP (SAML)

Advanced Identity Cloud serves as the IdP for Salesforce using SAML.

Validate by signing on to the Advanced Identity Cloud end-user UI to SSO into Salesforce.

Microsoft Entra ID (Azure AD) as OpenID provider

Configure social authentication by letting Microsoft Entra ID (formerly Azure AD) serve as the IdP to Advanced Identity Cloud using OIDC.

Validate by authenticating with Microsoft Entra ID and automatically be signed on to the Advanced Identity Cloud end-user UI.

Ping Identity as external authentication method for Microsoft Entra ID (Azure AD)

Configure Advanced Identity Cloud as an external authentication method for Microsoft Entra ID (formerly Azure AD).

Validate by using Advanced Identity Cloud as a second authentication factor for Microsoft Entra ID.

Pass-through auth (PTA) with Microsoft Entra ID (Azure AD)

Connect to Microsoft Entra ID (formerly Azure AD) in a journey to capture an end user’s password, after successful authentication, to store in Advanced Identity Cloud.

Validate by authenticating with Microsoft Entra ID in a PTA journey for Advanced Identity Cloud to capture the password. Then, sign on to the Advanced Identity Cloud end-user UI with the default login journey to show that Advanced Identity Cloud successfully stored the password.

Provision data from Active Directory (AD) using RCS

Provision users from an on-premises data source, AD, using a remote connector server (RCS).

Validate from AD by using Advanced Identity Cloud.