--- title: Managing PingOne connections description: Add a credential from your PingOne environment to the PingAccess administrative console to establish a connection between PingAccess and PingOne Protect. component: pingaccess version: 9.0 page_id: pingaccess:pingaccess_user_interface_reference_guide:pa_p1_connection_overview canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_user_interface_reference_guide/pa_p1_connection_overview.html revdate: June 14, 2024 section_ids: about-this-task: About this task adding-a-pingone-connection: Adding a PingOne connection steps: Steps result: Result: next-steps: Next steps editing-a-pingone-connection: Editing a PingOne connection steps-2: Steps deleting-a-pingone-connection: Deleting a PingOne connection steps-3: Steps pingone-connection-field-descriptions: PingOne connection field descriptions advanced-settings: Advanced Settings --- # Managing PingOne connections Add a credential from your PingOne environment to the PingAccess administrative console to establish a connection between PingAccess and PingOne Protect. ## About this task PingOne connections are currently only used as part of PingAccess's integration with PingOne Protect. For a more detailed explanation of this integration, see [PingOne Protect integration](../agents_and_integrations/pa_p1risk_policy_eval_integration.html). You must create a PingOne connection before you can create a [risk policy](pa_risk_policies_overview.html) in PingAccess. A PingOne connection makes it possible for PingAccess to receive risk evaluations from PingOne Protect. To create or manage PingOne connections through the PingAccess administrative console, see: ## Adding a PingOne connection ### Steps 1. Configure PingOne Protect for connectivity with PingAccess: 1. In your PingOne administrative environment, go to **Integrations → PingFederate**. Currently, you must use a PingFederate connection because PingAccess does not have one of its own. 2. Expand an existing connection or click the **[icon: plus, set=fa]**icon to create a new one. 3. On the **Overview** tab, click the **[icon: plus, set=fa]**icon next to **Credentials**. 4. Click the **Copy to clipboard** icon, then click **Done**. #### Result: This copies a JSON Web Token (JWT) *(tooltip: \
\

An IETF standard container format for a JSON object used for the secure exchange of content, such as identity or entitlement information. You can find the industry standard in \RFC 7519\.\

\
)* to your clipboard that contains information on your PingOne environment. 2. Configure PingAccess for connectivity with PingOne Protect: 1. In PingAccess, go to **Settings → System → PingOne Connections** and click **+Add PingOne Connection**. 2. Complete the fields. For more information, see [PingOne connection field descriptions](pa_p1_connection_field_descriptions.html). 3. Click **Save**. ### Next steps After you've created a connection, you can assign it to a specific risk policy through the **Risk Policies** page. For more information, see [Adding a risk policy](pa_adding_a_risk_policy.html). ## Editing a PingOne connection ### Steps 1. Go to **Settings → System → PingOne Connections**. 2. Click the **Expand** icon to view more details about the connection that you want to edit. 3. On the **Properties** tab, click the **Pencil** icon. 4. Make the required changes. For more information, see [PingOne connection field descriptions](pa_p1_connection_field_descriptions.html). 5. Click **Save**. ## Deleting a PingOne connection ### Steps 1. Go to **Settings → System → PingOne Connections**. 2. Click the **Expand** icon to view more details about the connection that you want to delete. 3. Click the **Delete** icon. 4. Click **Delete**. ## PingOne connection field descriptions The following table describes the fields available for managing PingOne connections on the **PingOne Connections** tab in the PingAccess administrative console. | Field | Required | Description | | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Yes | A unique name for this PingOne connection. | | **Description** | No | An optional description for this PingOne connection. | | **Credential** | Yes | In the **Credential** field, paste the JWT *(tooltip: \
\

An IETF standard container format for a JSON object used for the secure exchange of content, such as identity or entitlement information. You can find the industry standard in \RFC 7519\.\

\
)* that you copied to your clipboard in step 1d of [Adding a PingOne connection](pa_adding_a_p1_connection.html). This credential is necessary to establish a connection with PingOne. Whenever you save a PingOne connection, PingAccess validates the credential you specified to make sure it can communicate with the associated PingOne environment. | ### Advanced Settings To configure advanced settings on a PingOne connection, expand the **Show Advanced Settings** section at the bottom of the **PingOne Connections** tab. These settings are optional. | Field | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | **Trusted Certificate Group** | The group of certificates that you want to use to establish trust when using this connection to communicate with PingOne. | | **Use Proxy** | Select the **Use Proxy** check box if you plan to use a proxy to send HTTPS requests to PingOne. |