Repository navigation
Conversation
…ed without SPNEGO Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The referenced SCM instructions use incorrect configuration property names.
1 open finding
What changed in this PR
Documents the unauthenticated DB checkpoint risk when SPNEGO is disabled.
Changes:
- Describes affected OM and SCM endpoints.
- Recommends SPNEGO or network restrictions.
| File | Description |
|---|---|
docs/.../03-https.md |
Adds checkpoint endpoint security guidance. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…names Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Generated-by: Claude Code (Opus 5.5)
What changes were proposed in this pull request?
The OM and SCM web servers authenticate requests only when HTTP Kerberos (SPNEGO) is enabled, which is off by default. The admin check of the DB checkpoint endpoints needs an authenticated caller, so it is applied only with SPNEGO.
This PR adds a paragraph to the "Default authentication" section of the HTTP authentication page that says so, and tells operators of a secure cluster to enable SPNEGO for OM and SCM or restrict network access to their HTTP ports. Only
docs/(Next) is changed.The matching config descriptions and
THREAT_MODEL.mdchange are in apache/ozone#11439.What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-16759
How was this patch tested?
Ran
markdownlintandcspellon the edited page locally. The full site build is left to CI.🤖 Generated with Claude Code