This article discusses Auth0 provisioning of an application during the Okta Integration Network (OIN) workflow and the potential for rate limit errors during that process. 

• OIN provisioning in the Auth0 Dashboard
• Okta Integration Network (OIN)
• Creating an Auth0 Application and enrolling in OIN

When an admin clicks the Okta Integration Network tab for a newly created application, a step-by-step guide will be displayed. On the step Configure Integration Profile, the admin has the ability to configure a connection to be used for 3rd party admin provisioning:

When a connection is selected, an automatic Management API call is triggered to unlink this application from all other connections in that tenant. By default, an application created in the Auth0 dashboard has all available connections enabled. The following logs will be generated in the logs section of the dashboard:

If a tenant has a high volume of connections, this may trigger the rate limits for the relevant Management endpoint: /api/v2/connections/con_keTz9z47hQ7uKqUh/clients. The particular rate limit will be in accordance with the Auth0 accounts subscription plan and can be reviewed in Rate Limit Configurations.

As an example, an Enterprise account's Management API rate limit is 50 Burst requests and 16 RPS sustained. When an Enterprise admin has over 50 connections, this triggers a rate limit error when attempting to complete the OIN setup.

To mitigate this issue, please follow the steps below:

1. Navigate to Tenant Settings > Advanced in the dashboard.
2.  Scroll down to the Settings section. 
3. The toggle Enable Application Connections can be disabled, which will prevent a newly created application from having all connections enabled by default.