Connector maturity: Beta. See Connector maturity.
Description
The IBM Security Verify connector uses the IBM Security Verify REST API to discover user identities, groups, and role assignments within an IBM Security Verify (ISV) SaaS or on-premises deployment. It authenticates using OAuth 2.0 client credentials and provides visibility into enterprise identity governance across cloud and on-premises applications.
System Type Classification
| Field | Value |
|---|
| System Type | Directory Service |
| Default Scan Priority | 10 |
Version Support
| OrbisID Edition | Supported |
|---|
| Community | No |
| Pro | Yes |
| Enterprise | Yes |
Supported Protocol
| Protocol | Port | Notes |
|---|
| REST API (HTTPS) | 443 TCP | OAuth 2.0 client credentials flow |
What OrbisID Discovers
| Data | Source |
|---|
| User identities | GET /v2.0/Users (SCIM 2.0 endpoint) |
| Groups | GET /v2.0/Groups (SCIM 2.0 endpoint) |
| Group memberships | members array in group records |
| User enabled state | active attribute |
| Access roles | GET /v1.0/accesspolicies |
NHI Subtype Classification
This connector does not yet assert an NHI (Non-Human Identity) subtype directly from IBM Security Verify's API — accounts are classified via the naming-pattern catalogue rules and AI classifier (Tier B) only. IBM Security Verify's Applications API (registered OIDC/SAML/API clients) is a separate admin surface, distinct from the SCIM /Users endpoint this connector already queries, and is the likely real signal for a future connector-asserted classification — but the exact endpoint was not confirmed against a live tenant, so it was not implemented here.
Connection Requirements
Required Permissions
Register an API client in IBM Security Verify and assign read permissions.
Minimum permissions:
readUsers — enumerate user identities
readGroups — enumerate groups and memberships
manageAllAuthorizations — read access policies (optional, for full role discovery)
Credential Mapping
| OrbisID Field | Value |
|---|
credential.username | ISV OAuth 2.0 Client ID |
credential.password | ISV OAuth 2.0 Client Secret |
system.ipAddress (the IP Address / Hostname field) | ISV tenant hostname (e.g., myorg.verify.ibm.com) |
Network Requirements
The OrbisID server must have HTTPS access to the IBM Security Verify tenant on port 443.
Configuration Steps
- In the IBM Security Verify admin console, navigate to Security → API Access → Add API Client
- Grant
readUsers and readGroups entitlements
- Note the Client ID and Client Secret
- 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., IBM Security Verify – Production) |
| OS Type | IbmSecurityVerify |
| System Type | Directory Service |
| IP Address / Hostname | ISV tenant hostname |
| Credential | The API client credential |
- Click Test Connection
- Click Save
Troubleshooting
| Symptom | Likely Cause | Resolution |
|---|
Authentication failed | Invalid client credentials | Verify the Client ID and Secret in the ISV console |
| No users returned | Missing readUsers permission | Add readUsers entitlement to the API client |
403 Forbidden | Entitlements not granted | Review and update API client entitlements |
| Tenant not found | Incorrect hostname | Verify the ISV tenant URL |