You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2017/04/04 19:05:41 UTC
[jira] [Created] (NIFI-3670) ListenSyslog should expose a Client
Auth property for TLS/SSL
Bryan Bende created NIFI-3670:
---------------------------------
Summary: 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.1, 1.1.1, 0.7.1, 1.1.0, 1.0.0
Reporter: Bryan Bende
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)