---
title: Connecting a service
description: Connect PingOne Authorize to HTTP, PingOne Connector, or LDAP Gateway services to define data integrations.
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1_az_connecting_a_service
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1_az_connecting_a_service.html
revdate: April 27, 2026
section_ids:
  steps: Steps
  choose-from: Choose from:
  next-steps: Next steps
---

# Connecting a service

Connect PingOne Authorize to HTTP, PingOne Connector, or LDAP Gateway services to define data integrations.

Service connections in PingOne Authorize enable you to augment authorization events with real-time data. For example, you can use signals obtained from a risk service connection in a policy that determines whether a device requires step-up authentication.

## Steps

1. In the PingOne admin console, go to **Authorization > Trust Framework**.

2. On the **Services** tab, click the **[icon: plus, set=fa]**icon.

3. Define general information for the service:

   1. Enter a unique **Name** for the service.

      The following characters aren't allowed in the service name:

      * Period (.)

      * Curly bracket ({ })

      * Pipe (|)

   2. (Optional) In the **Description** field, enter a description of the service's purpose.

      The description is only visible on the **Services** tab, but it can help policy authors understand how to use the service in policies.

   3. (Optional) To nest the service under a parent in the tree, select a **Parent** service.

      Nesting groups related services together. You can move the service to another location in the tree by selecting a different parent service. To remove nesting, click the **Delete** icon and leave the **Parent** blank.

4. Select a **Service Type**.

   ### Choose from:

   * **None**: This is for a parent service. Nest other services under a parent to help organize services in the tree structure. There are no additional settings to complete for this type of service. If you select **None**, skip to step 9.

   * **HTTP**: Connects to HTTP endpoints accessible over the public internet. Learn more about HTTP service settings in [Connecting an HTTP service](p1_az_connecting_an_http_service.html).

   * **Connector**: Connects to PingOne services. Learn more about Connector service settings in [Connecting to PingOne Protect](p1_az_connecting_p1_risk.html).

   * **LDAP Gateway**: Connects to an external LDAP directory, such as PingDirectory or Microsoft Active Directory. Learn more about LDAP Gateway service settings in [Connecting an LDAP Gateway service](p1_az_connecting_a_gateway_service.html).

5. (Optional) In the **[Value Settings](p1_az_value_settings.html)** section, define the data **Type** for the data returned by the service.

   * The default data type for HTTP services is **String**.

   * Because Connector services always return JSON, the default data type is **JSON**, and you can't change it.

   * The default data type for LDAP Gateway services is **String**.

6. []()(Optional) In the **Timeout Settings** section, enter a **Request Timeout** value if you want to change the number of milliseconds that PingOne Authorize waits for a service request to complete.

   The request timeout range is 0 - 3000 milliseconds and the default is 2000 milliseconds. If the timeout elapses before there is a successful service response, PingOne Authorize cancels the service request, resulting in a timeout error.

7. (Optional) In the **Rate Limits** section, enter a **Requests per Second** value to change the maximum number of requests that decision points can make to the service per second.

   The default value is 1000000.

   |   |                                                                                      |
   | - | ------------------------------------------------------------------------------------ |
   |   | The **Concurrent Requests** field has been deprecated and changing it has no effect. |

8. []()(Optional) Enable caching for the service.

   [Caching](p1_az_service_caching.html) improves system performance by storing data returned from a service and reusing it on subsequent service requests until the cache expires.

   ![Screen capture showing the Enable Caching checkbox and Time to Live field in service Cache Settings.](_images/p1az-service-cache-settings.png)

   1. Select the **Enable Caching** checkbox.

   2. For **Time to Live**, enter the number of minutes that you want to store data retrieved from the service in the cache.

      The maximum value is 1440 minutes or 1 day.

   3. []()(Optional) To exclude HTTP headers from the service cache key, under **Cache Key Exclusions**, click **+ Header** and select a header to exclude.

      Excluding headers from the cache key prevents unnecessary cache misses caused by headers that are unique to each request, vary occasionally, or have no effect on the service response. Learn more in [Service caching](p1_az_service_caching.html).

      |   |                                                                                                                  |
      | - | ---------------------------------------------------------------------------------------------------------------- |
      |   | You must define headers in **Headers** service settings before adding them to the **Cache Key Exclusions** list. |

9. Click **Save Changes**.

   |   |                                                                                                                                                                  |
   | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | You can copy a service for reuse by selecting **Make Copy** in the service's hamburger menu. If you copy a service with children, only the parent is duplicated. |

## Next steps

Test the service connection. Learn more in [Testing Trust Framework elements](p1_az_testing_tf_elements.html).