[
https://issues.apache.org/jira/browse/NIFI-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876621#comment-16876621
]
ASF subversion and git services commented on NIFI-6174:
-------------------------------------------------------
Commit 41663929a4727592972e6be04b3c516a752e760e in nifi's branch
refs/heads/master from DimDroll
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4166392 ]
NIFI-6174: Add ClientAuth property to ListenBeats
This closes #3539.
Signed-off-by: Koji Kawamura <[email protected]>
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)
