Additional Settings

Enter a API Rate Limit for the maximum API rate limit threshold as the maximum permissible call number. For pre-existing sources, if you have the maxPermissibleCalls attribute, you can change its value. This value is expressed as a percentage without the percent symbol (%). By default, it is 90.


This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/okta/help/integrating_okta/additional_settings.html

This page could use a lot more detail:

Select Disable Group Caching to disable the cache creation of user groups. The connector fetches user profiles followed by groups during account aggregation.

It’s unclear whether the second sentence above applies when Disable Group Caching is selected or unselected.

The Okta Source creates a group cache to improve aggregation performance, as exemplified in the following steps:

  1. The source creates a cache of users connected to groups.
  2. The source then fetches the user profiles.
  3. The source maps the groups of the fetched user profiles to the cache created originally.

It would be helpful if the endpoints for those calls were spelled out so we can better understand the order of operations and how the objects relate to each other.

This cache creation works best in environments where there is are fewer connections between users and groups. Because of API limitations, the cache creation can take a longer time the more connections there are. To skip the cache creation and fetch the user profiles followed by groups, enable Disable Group Caching field.

Grammar issues, but also what do we mean by fewer connections? How many is fewer?

Select Enable Group Skinny User to enable the skinny_user endpoint to fetch the groups connected to a user in the Okta source. This attribute is applicable only for caching the approach of account aggregation.

What is the expected result of this? Should this make aggregations take longer, or take less time? By This attribute is applicable only for caching the approach of account aggregation, does this mean that the Enable Group Skinny User option only applies when Disable Group Caching is not selected?

Enable Partitioning to process the data in parallel across multiple threads.

  1. Enter a Number of Partitioning Thread value. By default, it is 2.If the VA is configured for multiple CPU cores, it can be configured for a higher number of partition threads to improve performance even further.

While 2 is the default, what is the maximum number of threads for this connector when running on a VA? Or when using the SaaS connector?

Thanks!

Hi Mark! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-6622

1 Like