[
https://issues.apache.org/jira/browse/NIFI-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990883#comment-15990883
]
ASF subversion and git services commented on NIFI-3670:
-------------------------------------------------------
Commit da6ad4f3bcdeb43783aafa9f8942c5fa2a7da20b in nifi's branch
refs/heads/master from [~trixpan]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=da6ad4f ]
NIFI-3670 - Expose the control of ListenSyslog's CLIENT_AUTH property to DFM
This closes #1720.
Signed-off-by: Bryan Bende <[email protected]>
> ListenSyslog should expose a Client Auth property for TLS/SSL
> -------------------------------------------------------------
>
> Key: NIFI-3670
> URL: https://issues.apache.org/jira/browse/NIFI-3670
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0, 0.7.1, 1.1.1, 1.0.1
> Reporter: Bryan Bende
> Assignee: Andre F de Miranda
> Priority: Minor
>
> ListenSyslog 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)
