---
title: Delinea Secret Server integration
description: Connect Delinea Secret Server to PingOne Privilege as a secrets hub for secure credential injection.
component: privilege
page_id: privilege:integrations:secrets-hubs/delinea-secret-server
canonical_url: https://docs.pingidentity.com/privilege/integrations/secrets-hubs/delinea-secret-server.html
llms_txt: https://docs.pingidentity.com/privilege/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: September 12, 2026
section_ids:
  configure-delinea-secret-server-integration: Configure Delinea Secret Server integration
  before-you-begin: Before you begin
  add-delinea-secret-server-as-a-secrets-hub: Add Delinea Secret Server as a secrets hub
  use-cases: Use cases
  rotating-secrets: Rotating secrets
  auditing-secret-usage: Auditing secret usage
---

# Delinea Secret Server integration

Connect Delinea Secret Server to PingOne Privilege as a secrets hub so that users can use secrets stored in Delinea Secret Server.

## Configure Delinea Secret Server integration

### Before you begin

Ensure you have the following:

* A deployed Delinea Secret Server set up with the policies and permissions your organization requires.

* Delinea credentials that PingOne Privilege can use to read the secrets it will inject, such as an API user account.

* Your Delinea credentials have read access to the secrets you'll map to targets, as well as rotation permissions if you want automatic rotation on session check-in.

### Add Delinea Secret Server as a secrets hub

1. In the PingOne Privilege admin console, go to **Secrets > Hubs**.

2. On the **Secrets Hubs** page, click the **Add Hubs** tab.

3. In the **Delinea** tile, click **Integrate [icon: plus, set=fa]**.

4. Enter a **Name** and optional **Description** for the **Hub**. Click **Next**.

5. Follow the instructions in the wizard for the configuration steps in Delinea. Click **Next**.

6. Complete the following required credentials from your Delinea Secret Server instance:

   * **Server URL**

   * **Client ID**

   * **Client Secret**

7. Click **Next**.

8. Review the summary, including any filters, and submit the configuration.

9. Validate the connection:

   1. In the **Active Hubs** tab, locate the new hub.

   2. Open the hub and verify that its connection status is **Synced**.

      |   |                                                                                                                                                                                         |
      | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | A new or resynchronizing hub might temporarily display a pending status or a **Syncing…​** indicator. If the status is **Error**, review the hub configuration and Delinea permissions. |

## Use cases

You can use the Delinea Secret Server hub for the following use cases.

### Rotating secrets

When a session that used an injected secret checks in, PingOne Privilege triggers the configured rotation operation for that secret in Delinea Secret Server.

This means:

* The secret used by the checked-in session is rotated in Delinea Secret Server without manual intervention.

* The next session that requests the secret receives the current value.

Automatic rotation must be configured for the secret in Delinea Secret Server, and the credentials used by PingOne Privilege must have the permissions required for the configured rotation operation.

### Auditing secret usage

Each use of a secret is recorded as an audit event in the PingOne Privilege audit trail. The event includes the secret name as metadata.

1. In the PingOne Privilege admin console, go to **Activity > Activity Logs**.

2. Use the available filters to locate the session or user activity.

3. Review the audit event and confirm that it includes the name of the secret that was used.