Maximum Number of Policies Allowed on an Okta Authorization Server
Last Updated:
Overview
The Okta Admin Console restricts the number of access policies that can be displayed and created to 50 per Authorization Server. Administrators can bypass this limit and create additional policies using the Okta API. However, configuring more than 100 policies on a single Authorization Server may degrade performance.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- API Access Management
- Authorization Servers
Solution
What is the limit on the number of policies per Okta Authorization Server?
Okta does not enforce a hard limit on the total number of access policies that an Authorization Server can contain. However, the Okta Admin Console enforces a display and creation limit of 50 access policies per Authorization Server.
How do administrators manage additional policies beyond the Admin Console limit?
Administrators must use the Okta API to create, access, and manage policies when the Authorization Server exceeds the 50-policy limit in the Admin Console. Generate an Okta API token, identify the Authorization Server ID, and make HTTP requests to the policies endpoint to manage additional policies.
- Generate an Okta API token from the Okta Admin Console.
- Identify the ID of the target Authorization Server.
- Make HTTP requests (such as
GET,POST,PUT, orDELETE) to the/api/v1/authorizationServers/<authServerId>/policiesendpoint to manage the policies.
NOTE: Configuring more than 100 policies on a single Authorization Server might cause performance issues.
