Integrations / Ping Identity

Ping Identity

PingOne identity management for environments, populations, users, groups, applications, and group memberships.

OAuth 2.0

Indexes

Spend

AI estate

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spendPartial Discovers shadow AI Yes Runs actions Yes Real-time events No

Before you connect

Prerequisites

A PingOne (Ping Identity) environment you can administer.

Environment admin who can create a Worker app or API token.

Vendor setup

Get the credential

Open the environment

In PingOne, open the environment Telara should read. Copy the environment id from the environment overview URL or Properties.

Create a Worker application

Go to Applications → Add Application → Worker. Issue a client secret. Grant the permissions this page lists. Copy the token or client credentials the Connect form asks for.

Paste in Telara

Settings → Integrations → Ping Identity. Paste the API token and the environment API root Telara asks for (the host plus environment id).

In Telara

Connect in Telara

OAuth 2.0

PingOne Worker application client-credentials OAuth. Supply the environment ID, client ID and client secret; grant least-privilege administrator roles to the worker app. It intentionally has no browser authorization URL because a worker app is userless.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Environment Id
Base Url

API key

PingOne API access token. Store base_url as the environment API root, for example https://api.pingone.com/v1/environments/{environment_id}.

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for

API token

Knowledge

What gets indexed

Resource	Coverage
Users	Partial — not every record the vendor holds is synced
Group	Partial — not every record the vendor holds is synced
Application	Partial — not every record the vendor holds is synced

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

Sync

Freshness & sync

Resource	Lag	Deletions
Users	Up to 1 day	Removed records disappear on the next full sync
Group	Up to 1 day	Removed records disappear on the next full sync
Application	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Users, Group, Application.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

PingFederate on-prem is not this connector unless the form says so.

A Worker app in the wrong environment lists the wrong populations.