[
https://issues.apache.org/jira/browse/NIFI-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807915#comment-16807915
]
Dima Kovalyov commented on NIFI-6174:
-------------------------------------
I've re-compiled NiFi with ListenBeats that includes changes made in:
https://issues.apache.org/jira/browse/NIFI-3794
https://issues.apache.org/jira/browse/NIFI-3670
And it works. I want to contribute it in NiFi to make this change ship withÂ
regular release.
> ListenBeats should expose a Client Auth property for TLS/SSL
> ------------------------------------------------------------
>
> Key: NIFI-6174
> URL: https://issues.apache.org/jira/browse/NIFI-6174
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Dima Kovalyov
> Priority: Major
>
> ListenBeats currently hard codes the client auth to REQUIRED when creating an
> RestrictedSSLContext:
> {code:java}
> sslContext =
> sslContextService.createSSLContext(SSLContextService.ClientAuth.REQUIRED);
> {code}
> It should expose a Client Auth property like ListenTCP does and use that:
> {code:java}
> public static final PropertyDescriptor CLIENT_AUTH = new
> PropertyDescriptor.Builder()
> .name("Client Auth")
> .description("The client authentication policy to use for the SSL
> Context. Only used if an SSL Context Service is provided.")
> .required(false)
> .allowableValues(SSLContextService.ClientAuth.values())
> .defaultValue(SSLContextService.ClientAuth.REQUIRED.name())
> .build();{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
