Advanced settings

Optional tuning settings held in the management agent's appsettings.json file.

Most installations never need to change these settings. Leave the defaults in place unless you've measured a reason to change them.

The settings live in:

C:\Program Files\Lithnet\Okta Management Agent\appsettings.json

Stop any active run profiles before editing the file, and restart the MIM Synchronization Service afterwards.

Keep the OktaMA object and change only the settings you need. If a setting isn't already present in the installed file, you can add it to that object:

{
  "OktaMA": {
    "UserListPageSize": 200,
    "UserImportConcurrency": 8,
    "GroupListPageSize": -1,
    "GroupImportConcurrency": 8
  }
}

Proxy configuration is not set in this file. It comes from the standard .NET environment variables described in Configuring an HTTP proxy.

UserListPageSize

Number of users requested per page. Default 200, which is also the Okta maximum. Use a positive value no greater than 200. A smaller page size means more requests for the same number of users.

GroupListPageSize

Number of groups requested per page. Default -1, which lets Okta choose. Set a positive value to fix it; Okta recommends no more than 200.

UserImportConcurrency

Maximum number of users processed at once after Okta returns them, including any factor requests the selected schema requires.

The default is twice the number of logical processors, capped at 8. A value below 1 is treated as 1.

Raising this can shorten an import when factor attributes are selected, because those are per-user API calls. It also puts more concurrent requests against the Okta rate limit. Read the import timings in the log before changing it.

GroupImportConcurrency

The same setting for groups, including the membership request made when member is selected. The same default and the same caution apply.

ConnectionLimit

Maximum HTTP connections held open per server. Default 1000. You should not normally need to change this.