Fetch times when using Salto with Okta are inherently tied to Okta's API rate limits. If you're experiencing prolonged fetch times or have been notified about exceeding rate limits during a Salto fetch operation, there are measures you can take. This article offers guidance on how to fine-tune both Salto's environment configuration and Okta API token settings to ensure smooth and efficient fetching.
Adjust Client Configuration in Salto
Salto's environment configuration file allows you to set parameters for both the number of concurrent requests and the number of requests per minute. Note, however, that these configurations are global and apply to all endpoints – they cannot be set individually for each endpoint.
client.rateLimit.get- This sets limits on the number of concurrent requests during a fetch. See Okta's documentation regarding concurrent limits to learn more about the concurrent limit for your account type.client.maxRequestsPerMinute- This controls the number of requests permitted per minute. We advise adjusting this value in line with your specific account type. See Okta's documentation on per-minute limits.
Configuration example
okta {
client = {
maxRequestsPerMinute = 700
rateLimit = {
get = 30
}
}
}Instructions
Navigate to the environment's settings.
Select "Edit configuration file" -
Modify the file with your preferred configuration settings -
Adjust API Token Settings in Okta
Okta API Tokens are, by default, configured to have 50% of an API endpoint's rate limit when created through the Admin Console. You can modify the default value for the token that Salto uses. You can do this through the admin console. For a comprehensive understanding and step-by-step instructions, please refer to Okta's documentation.
By following the above measures, you can significantly improve fetch times and minimize the chances of hitting rate limit walls.