Configure Connection
Okta guide
Create an API token, configure the tenant connection in NIM, and validate user retrieval and intended access changes.
Before you beginDirect link to Before you begin
Follow Okta's API token creation and privilege guidance. A token inherits its creator's administrator privileges, and changes to those privileges affect the token. Use an approved service account with the access needed for your process.
NIM requires Tenant URL and API Key.
Prepare API accessDirect link to Prepare API access
- Sign in using the administrator account approved for the integration.
- Follow the vendor's token creation instructions to generate an API token for NIM.
- Copy and securely store the token when it is displayed. Okta shows the value only once.
- If token network restrictions are configured, ensure that they allow the NIM server's public egress address.
- Confirm privileges for the user, group, and application-assignment operations your process requires.
Tokens expire after 30 days without use; each API call renews that period. Deactivating the token owner also deactivates its tokens. Plan token ownership and replacement accordingly.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add an Okta system, or select the existing system.
- Open Connection, enter the following settings, and save.
| NIM setting | Value |
|---|---|
| Tenant URL | The Okta tenant API address for your environment, using the format expected by the Connection screen. |
| API Key | The API token generated for the integration account. |
Test user retrievalDirect link to Test user retrieval
-
Select Test Connection. NIM attempts to retrieve users using:
GET /api/v1/users?limit=1&after=0 -
If the test fails, verify the Tenant URL, API token validity, owner privileges, network access, and any token network restrictions.
-
Collect the users, groups, memberships, and application assignments required by your process and validate identity and access mappings.
-
Test each intended user lifecycle or access change with safe records before enabling automation.
The connection test checks user retrieval. Validate other collection permissions and intended write operations separately.