[
https://issues.apache.org/jira/browse/NIFI-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15996832#comment-15996832
]
ASF GitHub Bot commented on NIFI-3794:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1746
+1 Looks good, since this is the same change we just made to ListenSyslog I
will go ahead and merge it to master for the 1.2 release
> ListenRELP should expose a Client Auth property for TLS/SSL
> -----------------------------------------------------------
>
> Key: NIFI-3794
> URL: https://issues.apache.org/jira/browse/NIFI-3794
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Andre F de Miranda
>
> ListenRELP currently hard codes the client auth to REQUIRED when creating an
> SSLContext:
> {code}
> sslContext =
> sslContextService.createSSLContext(SSLContextService.ClientAuth.REQUIRED);
> {code}
> It should expose a Client Auth property like ListenTCP does and use that:
> {code}
> 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
(v6.3.15#6346)
