Repository navigation
Restrict CouchDB user metadata access on 0.9.0 - #138
Merged
sciabarracom merged 1 commit intoOct 15, 2026
Merged
Conversation
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.
The user metadata database must not be readable anonymously or by ordinary CouchDB users. Apply an explicit admin-only membership ACL during initialization, including when the database already exists, while preserving its documents and repeatable initialization.
Validation on an isolated 0.9.0 lab with CouchDB 2.3: anonymous document,
_all_docsand_findrequests changed from HTTP 200 to 401; ordinary users receive 403; administrators retain access. Fresh and existing database initialization, repeated initialization and admin-api login passed. Three focused unit tests passed.Existing-state validation explicitly reran the metadata initializer. Merely replacing the operator image is not evidence that an existing database has been reconciled; rollout must run initialization and verify its ACL.