--- title: PingOne node (deprecated) description: The PingOne node establishes trust between PingOne and PingOne Advanced Identity Cloud by using a federated connection. component: auth-node-ref version: latest page_id: auth-node-ref:pingone:pingone canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone.html keywords: ["Authentication", "PingOne", "DaVinci"] superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone.html section_ids: example: Example availability: Availability inputs: Inputs dependencies: Dependencies node-ping-oidc-app-setup: Configure a PingOne OIDC application to connect to Advanced Identity Cloud configuration: Configuration outputs: Outputs outcomes: Outcomes --- # PingOne node (deprecated) The PingOne node establishes trust between PingOne and PingOne Advanced Identity Cloud by using a federated connection. This node performs an OIDC request to PingOne to delegate the user flow from Advanced Identity Cloud to PingOne using a standard OIDC redirect. | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | * This node is deprecated and will be removed in a future release. * Depending on your use case, use the following nodes instead: * [PingOne Identity Match node](pingone-identity-match.html) * [PingOne Create User node](pingone-create-user.html) * [PingOne Delete User node](pingone-delete-user.html) * [PingOne DaVinci API node](pingone-davinci.html) | ![pingone node diagram](_images/pingone_node_diagram.png) ## Example This example journey highlights the use of the PingOne node: ![ping one journey](_images/ping-one-journey.png) ## Availability | Product | Available? | | ------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes 1 | | Ping Identity Platform (self-managed) | Yes | 1 This functionality requires that you configure AM as part of a [Ping Identity Platform deployment](https://docs.pingidentity.com/platform/8.1/sample-setup/). ## Inputs Any data in the node state that must be sent to PingOne. ## Dependencies Before using the PingOne node, you must do the following: * [Configure a PingOne OIDC application to connect to Advanced Identity Cloud](#node-ping-oidc-app-setup) * Configure the [PingOne Service](pingone-service.html) * (Optional) If you plan to trigger a DaVinci flow from the PingOne node, follow the steps in [Integrating Flows into Applications](https://docs.pingidentity.com/davinci/integrating_flows_into_applications/davinci_how_to_implement_a_flow.html). ### Configure a PingOne OIDC application to connect to Advanced Identity Cloud Use the Applications page in the PingOne interface to add an application to connect to Advanced Identity Cloud. 1. Go to Applications > Applications. 2. Click +. 3. Create an application profile with these parameters: 1. Application name: Advanced Identity Cloud Federation. 2. Description (optional): Enables Advanced Identity Cloud federation with PingOne. 3. Select `OIDC Web App` as the Application Type. 4. Click Save. 5. After the application profile is created, go to the Configuration tab and click the pencil icon to edit the application. 1. In the PKCE Enforcement the drop-down, select `S256_REQUIRED`. 2. In the Token Endpoint Authentication Method drop-down, select `Client Secret Basic`. 3. Select Require Pushed Authorization Request. 4. Enter the Redirect URIs of your Advanced Identity Cloud AM instance. 6. Click Save, and then select Enable. ## Configuration | Property | Usage | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | PingOne Service | The ID of the PingOne Worker service for connecting to PingOne. | | ACR Values(optional) | For triggering a specific PingOne application policy. | | Username | The attribute that contains the name of the user for the object. | | State Inputs | A multi-value field to select specific attributes from node state to include in the federation request to PingOne. By default, the wildcard (\*) value includes the entire journey node state in the federation request to PingOne. | ## Outputs Any claims returned by PingOne during federation will be stored in the node state. ## Outcomes * `Account exists` If the account returned by PingOne during federation matches an existing account, and it is linked to the account in Advanced Identity Cloud. * `Account exists, no link` If the account returned by PingOne during federation exists in Advanced Identity Cloud, but it is not yet linked to the existing account in Advanced Identity Cloud. * `No account exists` If the account returned by PingOne during federation does not exist in Advanced Identity Cloud. - `Error` An error occurred causing the request to fail. Check the response code, response body, or logs to see more details of the error.