Investigating Application Rate Limits in Okta
Last Updated:
Overview
Application rate limits control the number of requests OAuth applications make to an Okta API endpoint, preventing any single application from monopolizing the limit. By default, Okta sets this consumption threshold to 50% of the total rate limit for each endpoint. Review these limits and adjust the consumption percentage in the Okta Admin Console to ensure sufficient capacity for specific applications.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- OAuth Applications
- Rate Limits
Solution
How are application rate limits investigated and adjusted?
Access the Okta Admin Console to review rate-limit information, identify endpoints with violations, and adjust the application's rate-limit consumption percentage.
- Access the Okta Admin Console and navigate to Reports > Rate Limits.
- Use the Rate Limit Dashboard to identify endpoints with violations.
- Select endpoints with any violations, bursts, or warnings to obtain additional details, such as filtering by Top Requests by Application. Filter by time period as needed.
- Copy the Application ID and paste it into the top-level search bar to review the application rate limit.
- Select the application name and then choose Application Rate Limits.
- Determine if the current rate limit is sufficient for the application.
- To increase the limit, select Edit and adjust the rate limit consumption percentage so the application can consume more of the rate limit for any given Okta API endpoint.
- Select Save.
NOTE: If the application rate limit for an application is set to 100%, the application can monopolize the endpoint rate limit, which could have a significant impact on performance depending on the affected endpoint.
