wozhenbang2004 opened a new issue, #16589: URL: https://github.com/apache/dubbo/issues/16589
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version 3.3.8-SNAPSHOT (`1cf125c42`), Netty 4.2.15.Final, Temurin 21.0.13, Linux. ### Steps to reproduce this issue Connect `NettyClient` or `NettyConnectionClient` to a TLS server with a trusted certificate whose SAN matches the target address. Configure the client certificate, key and CA through `SslConfig`. TCP connects, but the first TLS handshake fails: ```text SSLHandshakeException: (certificate_unknown) Hostname or IP address is undefined. ``` `SslClientTlsHandler` creates the engine with `newEngine(alloc)`, leaving the peer host unset. Netty 4.2 enables HTTPS endpoint verification by default. ### What you expected to happen A trusted certificate with a matching SAN should complete the handshake. A mismatched SAN should still be rejected. ### Anything else Related to #16200, which addresses the QUIC client. This affects the TCP client pipeline in `dubbo-remoting-netty4`. Reproduced with a CA-signed server certificate for `127.0.0.1`. Passing the connection address to the TLS engine allows the handshake; a certificate from the same CA with SAN `127.0.0.2` is still rejected. ### Do you have a (mini) reproduction demo? - [ ] Yes, I have a minimal reproduction demo to help resolve this issue more effectively! ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
