[ 
https://issues.apache.org/jira/browse/NIFI-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Koji Kawamura resolved NIFI-6174.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

Thank you [~dima_k] for your contribution! The PR has been merged to master.

Also, I've added NiFi Jira 'Contributor' role to your Jira account. You can 
assign yourself to any NiFi Jira issues now.

> 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
>            Assignee: Dima Kovalyov
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 40m
>  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)

Reply via email to