API Response Times for Authentication and Management APIs

Overview

This article clarifies whether API response times for authentication and management APIs are documented and part of the Service Level Agreement (SLA).

Applies To
  • Authentication
  • Management API
  • Service Level Agreement (SLA)
Solution

The SLA covers availability but not the response times. (See Service Levels for reference.)

For Private Cloud Customers

There are periodic internal tests for each private cloud release to detect regressions. Still, the results from these tests may not give the proper indication of what might be observed as the latency has many contributing factors that may be different in the setup.

For example:

  1. The customization in the tenant, like the rules/hooks/actions and custom DB login scripts
  2. The hosted page code and scripts
  3. The authentication flow used
  4. The number of users in the tenant
  5. The applied load
  6. The network latency between the test environment and the Auth0 servers
  7. The private cloud type (Basic, Performance, Performance Plus)

A load test can be performed, and, if any long delays are noticed, an investigation can be raised on how to improve it.

A Load Testing Policy exists for this process. For private cloud customers, the tests are typically approved quickly. Still, the same information is required to be shared before testing.

 

For Enterprise Public Cloud Customer

There are periodic internal tests to detect regressions. Still, the results from these tests may not give the proper indication of what might be observed as the latency has many contributing factors that may be different in the setup.

For example:

  1. The customization in the tenant, like the rules/hooks/actions and custom DB login scripts
  2. The hosted page code and scripts
  3. The used authentication flow
  4. The number of users in the tenant
  5. The applied load
  6. The network latency between the test environment and the Auth0 servers

A load test can be performed, and, if any long delays are noticed, an investigation can be raised on how to improve it. A Load Testing Policy exists for this process.


For Other Paid Public Cloud Customers

There are periodic internal tests for each to detect regressions. Still, the results from these tests may not give the proper indication of what might be observed as the latency has many contributing factors that may be different in the setup.

For example:

  1. The customization in the tenant, like the rules/hooks/actions and custom DB login scripts
  2. The hosted page code and scripts
  3. The used authentication flow
  4. The number of users in the tenant
  5. The applied load
  6. The network latency between the test environment and the Auth0 servers


A load test could help identify the average latency. Load testing is available for enterprise customers. If upgrading the plan to Enterprise is an option, a load test can be performed. See Load Testing Policy for more details.
 

Recommended content

No recommended content found...