---
title: GCP Secrets Manager integration
description: Connect GCP Secrets Manager to PingOne Privilege as a secrets hub for secure credential injection.
component: privilege
page_id: privilege:integrations:secrets-hubs/gcp-secrets-manager
canonical_url: https://docs.pingidentity.com/privilege/integrations/secrets-hubs/gcp-secrets-manager.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-gcp-secrets-manager-integration: Configure GCP Secrets Manager integration
  before-you-begin: Before you begin
  add-gcp-secrets-manager-as-a-secrets-hub: Add GCP Secrets Manager as a secrets hub
  use-cases: Use cases
  rotating-secrets: Rotating secrets
  auditing-secret-usage: Auditing secret usage
---

# GCP Secrets Manager integration

Connect GCP Secrets Manager to PingOne Privilege as a secrets hub so that users can use secrets stored in GCP Secrets Manager.

## Configure GCP Secrets Manager integration

### Before you begin

Ensure you have the following:

* A deployed GCP Secrets Manager set up with the policies and permissions your organization requires.

* GCP credentials that PingOne Privilege can use to read the secrets it injects, such as a service account.

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

### Add GCP Secrets Manager 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 **GCP** tile, click **Integrate [icon: plus, set=fa]**.

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

5. Select the type of GCP account you want to add as a **Hub**:

   * **Organization**

   * **Folder**

   * **Project**

6. Follow the setup wizard for the account type selected. Click **Next**.

7. Paste the Key JSON for the account type configured in the previous step. 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 GCP permissions. |

## Use cases

You can use the GCP Secrets Manager 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 GCP Secrets Manager.

This means:

* The secret used by the checked-in session is rotated in GCP Secrets Manager without manual intervention.

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

Automatic rotation must be configured for the secret in GCP Secrets Manager, 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 shows the secret name.