[
https://issues.apache.org/jira/browse/HBASE-28317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Beaudreault updated HBASE-28317:
--------------------------------------
Fix Version/s: 2.6.0
3.0.0-beta-2
Release Note: Adds RpcCallContext.getClientCertificateChain() for
accessing the SSL cert when TLS is enabled and a cert is available.
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the contribution [~charlesconnell] and review [~zhangduo]!
> 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)
