Connector maturity: GA. See Connector maturity.
Description
The Ping Identity connector uses the PingOne Management API to discover user accounts, groups, and group memberships within a PingOne environment. It authenticates using OAuth 2.0 client credentials via a Worker Application registered in PingOne. Pagination follows PingOne's cursor-based _links.next.href pattern.
System Type Classification
| Field | Value |
|---|
| System Type | Directory Service |
| Default Scan Priority | 10 (scanned first) |
Version Support
| OrbisID Edition | Supported |
|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|
| PingOne Management REST API (HTTPS + OAuth 2.0) | 443 TCP | Client credentials flow |
What OrbisID Discovers
| Data | Source |
|---|
| User accounts | GET /v1/environments/{envId}/users |
| User status (enabled/disabled) | enabled property |
| Population assignment | population.id — stored as attribute |
| Groups | GET /v1/environments/{envId}/groups |
| Group memberships | GET /v1/environments/{envId}/users?filter=memberOfGroups[id eq "{groupId}"] |
Connection Requirements
PingOne Worker Application
OrbisID authenticates as a Worker Application using the OAuth 2.0 client credentials grant. Worker Applications have direct API access without user interaction.
Steps to create the Worker Application:
- In the PingOne Admin Console, navigate to Applications → Applications
- Click Add Application → Worker
- Give it a name (e.g.,
OrbisID Scanner) and click Save
- Under the application, go to Configuration and note the Client ID and Client Secret
- Navigate to Roles and assign the following roles on the target environment:
| Role | Purpose |
|---|
| Identity Data Read Only | Read user accounts, groups, and populations |
Credential Mapping
| OrbisID Field | PingOne Value |
|---|
credential.username | Worker Application client ID |
credential.password | Worker Application client secret |
System Attributes
| Attribute | Required | Default | Description |
|---|
pingEnvironmentId | Yes | — | PingOne environment ID (UUID, found in Environment → Properties) |
pingRegion | No | NA | PingOne region: NA, EU, APAC, or CA |
Network Requirements
The OrbisID server (or On-Premise Agent) must have outbound HTTPS access to the PingOne API endpoints for your region:
| Region | API Base URL |
|---|
| NA | https://api.pingone.com |
| EU | https://api.pingone.eu |
| APAC | https://api.pingone.asia |
| CA | https://api.pingone.ca |
Configuration Steps
- Create the Worker Application in PingOne and assign the Identity Data Read Only role
- Note the Client ID and Client Secret from the application configuration
- Create a Credential in OrbisID:
- Username: Client ID
- Password: Client Secret
- Navigate to Systems → Add System
- Fill in the fields:
| Field | Value |
|---|
| Name | Descriptive name (e.g., PingOne – company.com) |
| Hostname | api.pingone.com (or region-specific URL, for reference) |
| OS Type | Ping Identity |
| System Type | Directory Service |
| Credential | The Worker Application credential |
- In the Connection Attributes section, set PingOne Environment ID (
pingEnvironmentId) and, if not using the NA region, Region (pingRegion)
- Click Test Connection
- Click Save
Detected Applications
Turn on Detect Applications (in the system's settings, under Detected Applications) to bring in the applications users sign in to through PingOne.
- Each application (except machine-to-machine Worker applications) is added as a child system named
<this system> - <application>, for example PingOne - Workday, with an access entitlement (Workday access).
- Who has access follows the application's access control: with Any group, members of any listed group (the group is shown as the path); with All groups, only users in every listed group (all of them shown as the path). An application with no group restriction is open to every user in the environment, so every user is listed. One limited to administrators only, with no groups, lists no users.
Detected applications are refreshed on every scan, archived when an application is removed (restored if it returns), and archived when Detect Applications is turned off. If applications cannot be read, the scan carries on and previously detected applications are left unchanged.
Link a detected application to the system that scans the same application directly, then use Reconcile access to compare the two - see Detected Applications.
Real-Time Account & Entitlement Events
Beyond periodic full scans, OrbisID can poll the PingOne Activities API on a short interval to detect account and group-membership changes near-real-time, or (opt-in) receive PingOne Webhooks for true push delivery. See Real-Time Events — Pro/Enterprise only; see that page's Limitations for detection coverage notes.
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|
PingOne authentication failed | Invalid client ID or secret | Verify the client ID and secret from the PingOne Worker Application |
PingOne access denied (403) | Missing Identity Data Read Only role | Assign the role on the environment in the Worker Application's Roles tab |
"Group membership resolution skipped" with "Invalid key=value pair (missing equal-sign) in Authorization header..." | Fixed in this connector — earlier versions called a nonexistent /groups/{id}/members endpoint, which fell through to PingOne's underlying AWS API Gateway default authorizer instead of a real 404 | Upgrade to the current connector version, which resolves membership via the Users API's memberOfGroups filter instead; no PingOne-side configuration change needed |
pingEnvironmentId not set | Attribute missing | Set PingOne Environment ID in the system's Connection Attributes section to the environment UUID |
| No users returned | Wrong environment ID or region | Verify the pingEnvironmentId matches the correct environment; check pingRegion |
| API call timeout | Wrong region | Verify pingRegion matches your PingOne account region |