Authorize createStateInZookeeper requests like the other blob operations - #9002
Merged
Conversation
reiabreu
approved these changes
Aug 23, 2026
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
2 participants
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.
createStateInZookeepercallsstate.setupBlob(...), which creates and mutates persistent znodes in the cluster ZooKeeper, with nocheckAuthorizationwhile every neighbouring blob endpoint has one. ExtendsNimbusTest.Scope: this makes the operation authorizer-visible and blockable. Under the shipped
SimpleACLAuthorizerdefaults (emptynimbus.users) any authenticated principal is still permitted, so this does not on its own restrict who may call it.