SPOG.AI integrates with Adobe to synchronize user and group inventory for centralized identity, license, and compliance visibility. The implemented connector uses Adobe OAuth Server-to-Server credentials and imports read-only directory records into SPOG.AI.
Key Features
| Capability | Description |
|---|---|
| User Inventory | Imports Adobe users and profile attributes. |
| Group Membership | Retrieves groups and associates membership context. |
| Domain Filtering | Limits ingestion to configured email domains. |
| OAuth Authentication | Uses Adobe client credentials and organization context. |
| Read-only Synchronization | Does not modify Adobe users, groups, licenses, or policies. |
How the Integration Works
The SPOG Appliance obtains an Adobe IMS access token with the configured client ID, client secret, and organization ID. It calls the configured user and group APIs over HTTPS, filters users by included domains, and imports normalized identity records into SPOG.AI.
Prerequisites
Before configuring the integration, ensure the following prerequisites are met:
- Tenant Admin authorization in SPOG.AI.
- Adobe Developer Console and Admin Console access for the correct organization.
- An OAuth Server-to-Server credential with read access to the required user and group APIs.
- Client ID, client secret, organization ID, and a list of included email domains.
- Outbound HTTPS access to Adobe IMS and API endpoints.
Configuration
1. Create Adobe OAuth Credentials
Create or open an Adobe Developer Console project and add the required user-management API.
- Choose OAuth Server-to-Server authentication; do not create a new JWT Service Account integration.
- Assign only the required product profiles or scopes.
- Copy the client ID, client secret, and organization ID.
2. Configure and Link the Integration
Add the Adobe integration in SPOG.AI.
- Enter the required credentials, organization ID, and included domains.
- Use API endpoint overrides only when required by the Adobe service or environment.
- Save the integration and link it to the required appliance.
Configuration Fields
Use the fields below when creating the integration in SPOG.AI.
| Field | Requirement | Description |
|---|---|---|
| client_id | Mandatory | Adobe OAuth client ID. |
| client_secret | Mandatory | Adobe OAuth client secret. |
| organization_id | Mandatory | Adobe organization identifier. |
| include_domains | Mandatory | Comma-separated email domains included in ingestion. |
| token_api | Optional | Adobe IMS token endpoint override. |
| users_api | Optional | Adobe users endpoint override. |
| groups_api | Optional | Adobe groups endpoint override. |
Security and Connectivity
- Use OAuth Server-to-Server credentials with least-privileged product profiles and read scopes.
- Store the client secret and organization context in a vault; rotate the secret regularly.
- Allow outbound HTTPS port 443 to Adobe IMS and service endpoints and require TLS 1.2 or later.
- Monitor failed token requests and unusual API activity.
Validation and Data Coverage
Obtain an Adobe IMS token, then retrieve a sample user or group through the configured API. Run the appliance job and confirm that users from included domains appear in SPOG.AI. Common failures are 401 for invalid credentials, 403 for missing product-profile access, and timeouts for blocked network access.
| Data | Coverage |
|---|---|
| Users | Adobe user and identity attributes returned by the configured API. |
| Groups | Adobe group records and membership context. |
| Filtering | Only users matching include_domains are ingested. |
| Not Implemented | The current connector does not ingest endpoints, alerts, webhooks, or configuration state and does not perform write operations. |
Uninstalling the Integration
- Delete the Adobe integration in SPOG.AI and unlink it from the appliance.
- Disable or delete the Adobe OAuth credential and remove its product-profile access.
- Remove obsolete API endpoint allowlist rules.