smengcl opened a new pull request, #11831: URL: https://github.com/apache/ozone/pull/11831
Generated-by: Claude Code (Opus 5.5) ## What changes were proposed in this pull request? Since HDDS-15152, `HttpServer2` always applies the enabled protocols to Jetty. When `ozone.ssl.enabled.protocols` is not set, it falls back to `hadoop.ssl.enabled.protocols`, which `core-default.xml` sets to `TLSv1.2`. So with no SSL protocol configuration, S3 Gateway and all component web UIs reject TLSv1.3. Before HDDS-10819, Jetty's defaults (TLSv1.2 and TLSv1.3) were used. This patch uses `hadoop.ssl.enabled.protocols` only when it is explicitly configured (`ConfigurationSource.isExplicitlySet`, which treats `core-default.xml` as a default resource), and otherwise defaults to `TLSv1.2,TLSv1.3`. `ozone.ssl.enabled.protocols` still takes precedence, and an explicit `TLSv1.2` (the case HDDS-15152 fixed) is still enforced. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-17542 ## How was this patch tested? Updated `TestHttpServer2SSL`: - Default config now accepts a TLSv1.3 only client (fails with `protocol_version` without the fix). - Unset config applies `TLSv1.2,TLSv1.3`. - Explicit `TLSv1.2` still rejects a TLSv1.3 only client. - New: `ozone.ssl.enabled.protocols` takes precedence over `hadoop.ssl.enabled.protocols`. 🤖 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]
