[
https://issues.apache.org/jira/browse/FLUME-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786338#comment-13786338
]
Charles Pritchard edited comment on FLUME-2204 at 10/4/13 5:11 PM:
-------------------------------------------------------------------
Expose it to the interceptor so that the interceptor can add it to the header
for the rest of the chain to process. Or just have a config option to add ssl
info into headers.
In this case, it's for multi-tenancy. We're currently passing oauth2 tokens and
verifying them upon receipt. Not as easy as simply distributing ssl client keys.
was (Author: downchuck):
Expose it to the interceptor so that the interceptor can add it to the header
for the rest of the chain to process. Or just have a config option to add ssl
info into headers.
> Expose Peer SSL Certificate in AvroSource
> -----------------------------------------
>
> Key: FLUME-2204
> URL: https://issues.apache.org/jira/browse/FLUME-2204
> Project: Flume
> Issue Type: Bug
> Reporter: Charles Pritchard
>
> AvroSource supports SSL connections, getPeerCertificateChain()[0] will expose
> the client SSL certificate. Through that getSubjectDN().getName() gives us
> very usable information.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
