[
https://issues.apache.org/jira/browse/HADOOP-19927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091452#comment-18091452
]
ASF GitHub Bot commented on HADOOP-19927:
-----------------------------------------
ferdelyi opened a new pull request, #8564:
URL: https://github.com/apache/hadoop/pull/8564
…server.need.client.auth.
Contains content generated by Claude Code
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [x] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [x] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> Add unit test for HttpServer2 mTLS enforcement via ssl.server.need.client.auth
> ------------------------------------------------------------------------------
>
> Key: HADOOP-19927
> URL: https://issues.apache.org/jira/browse/HADOOP-19927
> Project: Hadoop Common
> Issue Type: Test
> Reporter: Ferenc Erdelyi
> Assignee: Ferenc Erdelyi
> Priority: Minor
>
> HttpServer2 supports mutual TLS (mTLS) via the ssl.server.need.client.auth
> configuration key in ssl-server.xml. When this is set to true, the Jetty
> SslContextFactory is configured to require a client certificate, which is
> then validated against the
> server-side truststore (ssl.server.truststore.*).
>
> However, this code path has no unit test coverage. Existing tests in
> TestSSLHttpServer always set useClientCert=false and never call
> .needsClientAuth(true) on the builder, so the following behaviours are
> untested:
> - A client whose certificate is present in the server's truststore is
> accepted.
> - A client whose certificate is NOT present in the server's truststore is
> rejected with a TLS handshake failure.
>
> This JIRA adds TestSSLHttpServerMTLS, a focused integration test that:
> 1. Starts an HttpServer2 HTTPS server with needsClientAuth=true and a
> truststore loaded from ssl-server.xml.
> 2. Verifies that a trusted client (cert in the server truststore) receives
> HTTP 200.
> 3. Verifies that an untrusted client (cert not in the server truststore)
> receives an SSLHandshakeException.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
