[jira] [Commented] (HBASE-28777) mTLS client hostname verification doesn't work with OptionalSslHandler

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-28777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877836#comment-17877836 ] 

Hudson commented on HBASE-28777:
--------------------------------

Results for branch master
	[build #1149 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1149/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1149/General_20Nightly_20Build_20Report/]








(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1149/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> mTLS client hostname verification doesn't work with OptionalSslHandler
> ----------------------------------------------------------------------
>
>                 Key: HBASE-28777
>                 URL: https://issues.apache.org/jira/browse/HBASE-28777
>             Project: HBase
>          Issue Type: Bug
>          Components: rpc
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Andor Molnar
>            Assignee: Andor Molnar
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0-beta-2, 2.6.1
>
>
> Netty's OptionalSslHandler cannot carry hostport information to SslEngine, hence HBASE-27673 fixed the TLS-only case only. We need to have a custom handling for the plaintext-enabled TLS mode in order to support client hostname verification in that case too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)