This is an automated email from the ASF dual-hosted git repository.

adoroszlai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone-site.git


The following commit(s) were added to refs/heads/master by this push:
     new edeadd2758 HDDS-16682. [Auto] Update configuration documentation (#564)
edeadd2758 is described below

commit edeadd2758717f82d65af5987e0b4553265b4a26
Author: asf-ci-deploy <[email protected]>
AuthorDate: Tue Oct 6 18:19:50 2026 +0200

    HDDS-16682. [Auto] Update configuration documentation (#564)
---
 docs/05-administrator-guide/02-configuration/99-appendix.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md 
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index 4f2dc17612..4599811128 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -426,6 +426,7 @@ This page provides a comprehensive overview of the 
configuration keys available
 | `ozone.http.basedir` |  | `OZONE`, `OM`, `SCM`, `MANAGEMENT` | The base dir 
for the HTTP Jetty server. If this property is not configured, by default the 
directory named by `${ozone.metadata.dirs}`/webserver is used. While in a 
production environment, it's strongly suggested to point this at a different 
parent directory by setting this property. Under this directory Ozone creates 
and reuses a per-server subdirectory (named after the server) as Jetty's 
persistent temp directory; it is k [...]
 | `ozone.http.filter.initializers` |  | `OZONE`, `SECURITY`, `KERBEROS` | Set 
to org.apache.hadoop.security.AuthenticationFilterInitializer to enable 
Kerberos authentication for Ozone HTTP web consoles is enabled using the SPNEGO 
protocol. When this property is set, `ozone.security.http.kerberos.enabled` 
should be set to true. |
 | `ozone.http.policy` | HTTP_ONLY | `OZONE`, `SECURITY`, `MANAGEMENT` | Decide 
if HTTPS(SSL) is supported on Ozone This configures the HTTP endpoint for Ozone 
daemons: The following values are supported: - HTTP_ONLY : Service is provided 
only on http - HTTPS_ONLY : Service is provided only on https - HTTP_AND_HTTPS 
: Service is provided both on http and https |
+| `ozone.http.sni.host.check.enabled` | false | `OZONE`, `SECURITY`, 
`MANAGEMENT` | Whether the HTTPS endpoints of Ozone daemons require the 
request's Host header (or TLS SNI name) to be covered by the certificate the 
server serves. When this is false, a request whose name the certificate does 
not cover is still served with that certificate, which is how the HTTPS 
endpoints behaved before the Jetty 12 upgrade. Enabling the check rejects such 
a request with 400 "Invalid SNI", so it requir [...]
 | `ozone.https.client.keystore.resource` | ssl-client.xml | `OZONE`, 
`SECURITY`, `MANAGEMENT` | Resource file from which ssl client keystore 
information will be extracted |
 | `ozone.https.client.need-auth` | false | `OZONE`, `SECURITY`, `MANAGEMENT` | 
Whether SSL client certificate authentication is required |
 | `ozone.https.server.keystore.resource` | ssl-server.xml | `OZONE`, 
`SECURITY`, `MANAGEMENT` | Resource file from which ssl server keystore 
information will be extracted |


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to