Skip to main content

Optimizing Tulip Fetch Times with Okta Rate Limits

Support avatar
Written by Support
Updated over 4 months ago

Fetch times when using Tulip 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 Tulip fetch operation, there are measures you can take. This article offers guidance on how to fine-tune both Tulip's application connection configuration and Okta API token settings to ensure smooth and efficient fetching of your security application data.

Adjust Client Configuration in Tulip

Tulip's application connection 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.

Configuration example

okta {
client = {
maxRequestsPerMinute = 700
rateLimit = {
get = 30
}
}
}

Instructions

  1. Navigate to the application connection's settings page

  2. Select "Edit configuration file" under General > Application configuration


  3. 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 Tulip 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 when assessing and managing the security posture of your Okta application with Tulip.

Did this answer your question?