Add Support for Limiting M2M Usage via Tenant-Wide
Defaults and Client/Organization
Overrides
#537
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
This PR introduces support for configuring token quotas for M2M (client credentials) flows at the tenant, client, and organization levels.
Key Changes:
TokenQuota
struct used across tenant, client, and organization resourcesTenantDefaultTokenQuota
now allows configuring default quotas for bothclients
andorganizations
token_quota
fieldTokenQuotaClientCredentials
, which supports:enforce
: whether the quota is strictly enforced or just loggedper_day
andper_hour
limits for issued tokensUnsetting Quotas
To remove a previously set quota, send a
PATCH
request with anull
value:For implementation examples, refer to the Go SDK usage guide:
🔗 https://github.com/auth0/go-auth0/blob/main/EXAMPLES.md#providing-a-custom-user-struct
📚 References
🔬 Testing
PATCH
operations unset values correctly📝 Checklist