[
https://issues.apache.org/jira/browse/HBASE-28336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Connell updated HBASE-28336:
------------------------------------
Description:
I introduced a bug in HBASE-28317 that makes it useless. I tried to up-cast an
array of {{java.security.cert.Certificate}} to an array of
{{java.security.cert.X509Certificate}}, which doesn't work. I'll fix this in
this ticket. This bug causes a lot of log spam and makes
{{RpcCallContext.getClientCertificateChain()}} always return empty, but does
not otherwise break the HBase server.
I'm also immediately regretting my use of WARN logs when a certificate isn't
present, because it turns out this happens on connections from localhost, so
there's a lot of WARNs with stacktraces in the logs.
was:
I introduced a bug in HBASE-28317 that makes it useless. I tried to up-cast an
array of {{java.security.cert.Certificate}} to an array of
{{java.security.cert.X509Certificate}}, which doesn't work. I'll fix this in
this ticket.
I'm also immediately regretting my use of WARN logs when a certificate isn't
present, because it turns out this happens on connections from localhost, so
there's a lot of WARNs with stacktraces in the logs.
> Fix casting bug in NettyRpcServer introduced in HBASE-28317
> -----------------------------------------------------------
>
> Key: HBASE-28336
> URL: https://issues.apache.org/jira/browse/HBASE-28336
> Project: HBase
> Issue Type: Bug
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
>
> I introduced a bug in HBASE-28317 that makes it useless. I tried to up-cast
> an array of {{java.security.cert.Certificate}} to an array of
> {{java.security.cert.X509Certificate}}, which doesn't work. I'll fix this in
> this ticket. This bug causes a lot of log spam and makes
> {{RpcCallContext.getClientCertificateChain()}} always return empty, but does
> not otherwise break the HBase server.
> I'm also immediately regretting my use of WARN logs when a certificate isn't
> present, because it turns out this happens on connections from localhost, so
> there's a lot of WARNs with stacktraces in the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
