smengcl opened a new pull request, #11439: URL: https://github.com/apache/ozone/pull/11439
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. It is off by default, also when `ozone.security.enabled=true`. The admin check of the DB checkpoint endpoints (OM `/dbCheckpoint` and `/v2/dbCheckpoint`, SCM `/dbCheckpoint`) needs an authenticated caller, so it is applied only with SPNEGO. Neither the docs nor the config descriptions say so. Documentation only, no behavior change: - `ozone-default.xml`: the descriptions of `ozone.om.http.auth.type` and `hdds.scm.http.auth.type` now say that `kerberos` takes effect only when `ozone.security.http.kerberos.enabled` is true, and that with `simple` the admin check of `/dbCheckpoint` is not applied. - `THREAT_MODEL.md`: HTTP authentication is added to the controls that are off by default (section 5a) and to the operator hardening checklist (section 10). The website page is updated in a separate apache/ozone-site PR under the same Jira. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-16759 ## How was this patch tested? Documentation only. Checked with `xmllint` that `ozone-default.xml` is still well formed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
