Configure Connection
Adobe Cloud guide
Create a User Management API project in Adobe Developer Console, add its credentials to NIM, and verify access to your organization's users.
Before you startDirect link to Before you start
Use an Adobe account with the System Administrator role for the organization when creating the User Management API integration. Review Adobe's Developer Console setup guide for the project and credential workflow, and User Management API authentication for API-specific requirements. The Console guide illustrates Storage Management; select User Management API for this NIM connection.
NIM requires Client ID, Client Secret, and Organization ID from the same Adobe organization and project.
Create the Adobe API projectDirect link to Create the Adobe API project
- Sign in to Adobe Developer Console and select the organization NIM will manage.
- Create a project and choose Add API.
- Select User Management API and continue.
- Choose OAuth Server-to-Server, name the credential, and complete the configuration. Select applicable product profiles if prompted.
- Open the project's credential details. Obtain the Client ID, Client Secret, and Organization ID for the NIM connection.
Configure the NIM connectionDirect link to Configure the NIM connection
- In NIM Studio, open Systems > Overview and add an Adobe Cloud system, or select the existing system.
- Open its Connection screen.
- Enter the following values and save the connection.
| NIM setting | Value |
|---|---|
| Client ID | The API credential's client identifier from Adobe Developer Console. |
| Client Secret | The secret belonging to that credential. |
| Organization ID | The Adobe organization identifier, copied exactly from the project details. |
Test access and collect dataDirect link to Test access and collect data
- Select Test Connection. NIM requests the first page of users with
GET /v2/usermanagement/users/<organization id>/0, substituting the configured Organization ID. The final0is the first page number. - Confirm that the test succeeds. If it fails, check that all three values belong together, the secret is valid, and the project has User Management API access.
- Collect the system and inspect the users, groups, and group members needed by your process.
- Validate a limited population before enabling scheduled provisioning or membership changes.
A successful connection test establishes access to this user-list request. Verify the permissions and results of your intended write operations separately.