Skip to main content

ForgeRock / PingAM

Description​

The ForgeRock / PingAM connector uses the AM REST API to discover user identities, groups, and role assignments within a ForgeRock Access Management (now PingAM) deployment. It authenticates using an admin service account and enumerates user objects from the configured identity store realm, providing visibility into federated and local identities.

System Type Classification​

FieldValue
System TypeDirectory Service
Default Scan Priority10

Version Support​

OrbisID EditionSupported
CommunityNo
ProYes
EnterpriseYes

Supported Protocol​

ProtocolPortNotes
REST API (HTTPS)443 TCPAM SSO token or OAuth 2.0 authentication

What OrbisID Discovers​

DataSource
User identitiesGET /openam/json/users?_queryFilter=true
GroupsGET /openam/json/groups?_queryFilter=true
Group membershipsGET /openam/json/users/{id}/memberships
User enabled stateinetUserStatus attribute

Connection Requirements​

Required Permissions​

Create a dedicated AM service account with read access to the identity store.

Minimum permissions:

  • Read Users on the target realm
  • Read Groups on the target realm

Credential Mapping​

OrbisID FieldValue
credential.usernameAM administrator or service account username
credential.passwordAM account password
system.ipAddress (the IP Address / Hostname field)AM server hostname (e.g., am.example.com)
system.realmAM realm (e.g., / for root or /customers)

Network Requirements​

The OrbisID server must have HTTPS access to the ForgeRock AM server on port 443.

Configuration Steps​

  1. Create a dedicated service account in the AM console with read-only identity store permissions
  2. Create a Credential in OrbisID:
    • Username: AM service account username
    • Password: AM service account password
  3. Navigate to Systems → Add System
  4. Fill in the fields:
FieldValue
NameDescriptive name (e.g., ForgeRock AM – Production)
OS TypeForgeRock
System TypeDirectory Service
IP Address / HostnameAM server hostname
CredentialThe scanning credential
  1. Click Test Connection
  2. Click Save

Troubleshooting​

SymptomLikely CauseResolution
Authentication failedInvalid credentialsVerify the service account in the AM console
No users returnedIncorrect realmConfirm the realm path in the system configuration
403 ForbiddenMissing delegationGrant read delegation to the service account for the target realm
SSL certificate errorSelf-signed certificateImport the AM CA certificate into the OrbisID trust store