PingOne

Provisioning GCP with PingOne

Google Cloud Platform (GCP) is a suite of cloud computing services offered by Google. The GCP connection manages and synchronizes Google Workspace user accounts between Google Workspace and PingOne through the Google Admin SDK.

By using the GCP connection in PingOne, you can provision user accounts between Google Workspace and PingOne. Group, group membership, Google Cloud Identity and Access Management (IAM) role, project, and service principal provisioning aren’t supported.

Provisioning capabilities

The provisioning capabilities for the GCP connection are listed in the following table:

Resource Capability Description Inbound Outbound

User

Create

Generates a new Google Workspace user account in the destination.

Yes

Yes

Read

Retrieves or searches Google Workspace user attributes for synchronization.

Yes

Yes

Update

Modifies supported user attributes in the connected system.

Yes

Yes

Disable

Suspends or enables the Google Workspace user account through the Enabled attribute.

Yes

Yes

Delete

Deletes a Google Workspace user when deletion is configured and supported by the rule.

Yes

Yes

Group

Create, update, or delete

Google Groups aren’t supported.

No

No

Membership

Add and remove

Google Group membership synchronization isn’t supported.

No

No

IAM roles and projects

Manage

Google Cloud IAM roles, projects, and service principals aren’t supported.

No

No

Before you begin

Make sure that you have:

  • A Google Cloud project with a service account.

  • A Google Workspace domain that the GCP connection will manage.

  • The service account email address and a private key.

  • Domain-wide delegation configured for the service account.

  • The following Google Admin SDK user-management scope authorized for the service account: https://www.googleapis.com/auth/admin.directory.user.

  • A Google Workspace administrator account in that domain.

  • The Google Admin SDK API enabled for the Google Cloud project.

  • Users assigned to the PingOne population or group that you want to provision.

For initial setup, a Google Workspace Super Admin must configure domain-wide delegation and authorize the service account. The administrator user entered in the PingOne connection must have sufficient permissions to manage users in the configured domain.

Steps

  1. Create a GCP connection:

    1. In the PingOne admin console, go to Integrations > Provisioning.

    2. Click the Plus icon () and then click New Connection.

    3. Click Select for Identity Store.

    4. On the GCP tile, click Select.

    5. Click Next.

    6. Enter a Name and Description for the GCP connection.

    7. In Configure Authentication, enter the connection configuration values required for your Google Workspace domain:

      Field Value

      Domain name

      The Google Workspace domain, such as example.com.

      Private key

      The private key for the service account.

      Service account

      The service account email address.

      Admin user

      The Google Workspace administrator user to impersonate.

    8. Click Test Connection to verify that PingOne can establish a connection.

    9. Click Next.

    10. In Users Actions, configure the behaviors you need for the connection:

      Field Description

      Enable users creation

      Create Google Workspace users.

      Enable users updation

      Update mapped user attributes.

      Enable users disable

      Propagate the PingOne enabled state to Google Workspace.

      Enable users deprovision

      Apply the selected remove action when a user is removed from the rule scope or deprovisioned.

      Remove Action

      Select Delete to delete the Google Workspace user, as applicable.

      Deprovision on rule deletion

      Enable only when users should be deprovisioned if the provisioning rule is deleted.

    11. Click Save.

      Result

      The GCP connection appears in the Provisioning list after you save the connection.

    12. To enable the GCP connection, click the toggle at the top of the details panel to the right (blue).

      You can disable the connection by clicking the toggle to the left (gray).

  2. Create an inbound or outbound provisioning rule and select the existing GCP connection as the target or source. You can optionally add attribute mappings.

    • Inbound provisioning imports users from Google Workspace into PingOne when a separate inbound rule is configured.

    • Outbound provisioning sends users from PingOne to Google Workspace.

GCP attribute mapping

Use the following inbound and outbound mapping examples for the GCP rule configuration:

PingOne Directory GCP

Password

Password

Family Name

Family Name

Email Address/Username

Primary Email

Given Name

Given Name

Account ID

Account External ID

Enabled

Enabled

Validation

To validate the GCP connection:

  • View the sync status to review synchronization results and any errors.

  • Verify that the expected user accounts are created or updated in Google Workspace.

  • Confirm that the Google Workspace account is suspended when the PingOne user is disabled.

  • Confirm that a user is removed from the GCP rule scope when the user is deleted in PingOne.

GCP directory attributes

The following table lists common GCP attributes that can be mapped for user provisioning:

PingOne attribute Description

primaryEmail

The user’s primary Google Workspace email address.

password

The user’s password. This attribute is write-only.

givenName

The user’s given name.

familyName

The user’s family name.

enabled

Indicates whether the Google Workspace user account is enabled. The connector maps this value to the inverse suspended property.

externalIds

External identifiers associated with the user.

emails

Additional mail addresses.

organizations

Organization information associated with the user.

addresses

Address information associated with the user.

phones

Address information associated with the user.

relations

Relationship information associated with the user.

Synchronization

  • Outbound changes from PingOne to Google Workspace are supported through near-real-time provisioning.

  • Full sync or resync applies the current in-scope PingOne user state to Google Workspace.

  • Use a full sync or resync after creating or changing mappings, changing the population or user filter, recovering from failed synchronization, or validating a new connection.

  • Inbound synchronization can search and import Google Workspace users into PingOne through the configured inbound polling, full-sync, or resync behavior.

  • User synchronization in both directions requires separate inbound and outbound rules. It can’t be configured as one bidirectional rule.

Known GCP limitations and unsupported operations

User profile and lifecycle management

The following are known limitations with GCP user profiles and lifecycle management:

  • A new user can’t be created without primaryEmail, Password, givenName, and familyName.

  • Passwords are write-only and aren’t returned by search or read responses.

  • Unknown attributes are rejected instead of being silently ignored.

  • Multivalued attributes must use the expected Google Admin SDK structure.

Group and role management

The following are known limitations with GCP group and role management:

  • Group and membership object classes aren’t exposed.

  • The connection can’t create, update, rename, or delete Google Groups.

  • The connection can’t add or remove users from Google Groups or synchronize group membership.

  • The connection can’t manage Google Cloud IAM roles or permissions, projects, service principals, or other non-user Google Cloud resources.

  • Don’t add role or GroupNames mappings to a GCP rule.

Provisioning direction

Changes made directly in Google Workspace aren’t sent to PingOne through an outbound rule. They’re visible to PingOne only when an inbound rule is configured, and its polling or resynchronization runs.

Troubleshooting

The following are known troubleshooting scenarios with the GCP connection:

  • Ensure the connection is scoped to the configured Google Workspace domain.

  • The service account private key is confidential and must be stored and handled as a secret.

  • Domain-wide delegation and administrator impersonation are required. Incorrect delegation, scopes, or administrator privileges can cause authentication failures, such as unauthorized_clientext.

  • The connection supports user account CRUD operations but doesn’t provide group or membership synchronization.