[ https://issues.apache.org/jira/browse/HBASE-28317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812129#comment-17812129 ]
Hudson commented on HBASE-28317: -------------------------------- Results for branch master [build #1001 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1001/]: (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/1001/General_20Nightly_20Build_20Report/] (/) {color:green}+1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1001/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 jdk11 hadoop3 checks{color} -- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1001/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (x) {color:red}-1 client integration test{color} --Failed when running client tests on top of Hadoop 3. [see log for details|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1001//artifact/output-integration/hadoop-3.log]. (note that this means we didn't check the Hadoop 3 shaded client) > RpcCallContext should expose client's TLS certificate > ----------------------------------------------------- > > Key: HBASE-28317 > URL: https://issues.apache.org/jira/browse/HBASE-28317 > Project: HBase > Issue Type: Improvement > Reporter: Charles Connell > Assignee: Charles Connell > Priority: Minor > Fix For: 2.6.0, 3.0.0-beta-2 > > > At my employer we plan on using a coprocessor to log information about some > requests to HBase. For this to be useful to us, we need to know who each > request is coming from. We use HBase's TLS support with mutual authentication > to authenticate clients. I'd like a way to expose the client certificate used > on a request to coprocessors. For setups using Kerberos authentication, > RpcCall exposes the Kerberos principal shortname via {{getRequestUser()}}, so > this would be the TLS equivalent to that. -- This message was sent by Atlassian Jira (v8.20.10#820010)