Auth0
Built for Auth0 Enterprise Tenant ACL enforcement and customer-controlled Management API clients. QuotaGuard gives API and SCIM requests two stable IPv4 sources while existing Auth0 scopes and permissions remain in force.
QuotaGuard routes customer-controlled Auth0 Management API and SCIM traffic through the two fixed IPv4 addresses assigned to its subscription. Add both addresses to an Auth0 Tenant ACL with management scope so requests to /api/v2/* and /scim/* arrive from an approved network source. QuotaGuard has provided static-IP proxy service since 2013.
- Two-Minute QuotaGuard Setup: Add the QuotaGuard connection URL to the application, configure its HTTP client to proxy Auth0 requests, and register both dashboard IPs. Creating, monitoring, and enforcing the Auth0 policy is a separate cutover step.
- Native Management API Enforcement: Auth0 Tenant ACL can evaluate source-IP signals at the tenant edge and apply a rule to Management API and SCIM paths. Enterprise includes one ACL, while Enterprise with the Attack Protection add-on supports up to ten.
- Separate Token-Issuance Control: A Credentials Exchange Action can inspect the source of an M2M token request before Auth0 returns the token. It is optional and does not replace the Tenant ACL check on later Management API requests.
- Controlled Client Path: Use QuotaGuard for custom applications, jobs, and automation clients that can route the relevant HTTPS calls through a proxy. Auth0 scopes and permissions continue to determine what an issued token may do.
- Production-Grade Reliability: Each subscription receives two load-balanced static IPs with health checks and automated failover. Add both to Auth0 so either approved route can reach the tenant.
- Shield for the Customer-to-Proxy Hop: QuotaGuard Shield encrypts the connection from the application to the proxy while preserving the application's HTTPS session to Auth0 without decrypting its payload. Product selection does not make the Auth0 environment compliant by itself.
Auth0 plan note: Tenant ACL is an Enterprise feature. Enterprise includes one ACL, and the Attack Protection add-on raises the limit to ten. A Credentials Exchange Action is a separate token-issuance control and should not be described as request-level Management API filtering.