feat: auth0_managed curated blocklist support#1653
Draft
KartikJha wants to merge 1 commit into
Draft
Conversation
KartikJha
force-pushed
the
tfp-curated-blocklist-auth0-managed-dxcdt-1973
branch
from
July 20, 2026 16:20
0518e36 to
7459708
Compare
KartikJha
marked this pull request as draft
July 20, 2026 16:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔧 Changes
Adds support for Auth0-curated blocklists to the
auth0_network_aclresource and data source via a newauth0_managedattribute on rulematchandnot_matchblocks. This lets a rule match against Auth0-maintained lists (for exampleauth0.icloud_relay_proxyorauth0.low_reputation) without the practitioner enumerating IPs or ASNs.This is an Early Access feature: it requires the
advanced-breached-password-detectionentitlement and thetenant_acl_curated_blocklistsfeature flag to be enabled on the tenant.resource.go): newauth0_managedTypeListof strings on the rule match schema, with aValidateDiagFuncrequiring theauth0.<name>identifier form (e.g.auth0.icloud_relay_proxy).expand.go): readsauth0_managedintoNetworkACLRuleMatch.Auth0Managed, plus a newvalidateAuth0ManagedMutualExclusivitycheck that errors ifauth0_managedis set on bothmatchandnot_matchin the same rule, mirroring the API invariant.flatten.go): surfacesauth0_managedback into state on read.resource.go): create/update wrap 403 responses with a hint naming both required gates (entitlement + feature flag), but only when the rule actually usesauth0_managed.github.com/auth0/go-auth0to a pre-release build exposing theAuth0Managedfield onNetworkACLRuleMatch.matchblocklist and anot_matchallow-unless case demonstrating the mutual-exclusivity boundary).📚 References
go-auth0-v1 PR
🔬 Testing
TestAccNetworkACLAuth0Managed,TestAccNetworkACLAuth0ManagedValidation(resource) andTestAccNetworkACLDataSourceAuth0Managed(data source), with recorded HTTP fixtures undertest/data/recordings/.auth0_managedset on bothmatchandnot_match).make test-acc TESTARGS="-run TestAccNetworkACLAuth0Managed".📝 Checklist