fix: resolve api_keys and IP access config against the app's public tenant (backport to 11.4) - #1319
Merged
Merged
Conversation
…enant api_keys is app-scoped (@NotConflictingInApp), so the API key check and the IP allow/deny check now resolve their config from the app's public tenant rather than the raw request tenant, and fall back to it when the request tenant cannot be resolved. This keeps enforcement consistent across all of an app's tenants. (cherry picked from commit e8e99e8)
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
1 participant
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.
Automated backport of
e8e99e84onto11.4, released as 11.4.6.-x— each commit message carries its source SHA.chorecommit bumpsbuild.gradleto11.4.6and adds the[11.4.6]CHANGELOG section.Triggered from Backport by @tamassoltesz.