You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2022/04/08 19:54:00 UTC
[jira] [Updated] (NIFI-9897) Refactor GRPC SSL Configuration
[ https://issues.apache.org/jira/browse/NIFI-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-9897:
-----------------------------------
Status: Patch Available (was: Open)
> Refactor GRPC SSL Configuration
> -------------------------------
>
> Key: NIFI-9897
> URL: https://issues.apache.org/jira/browse/NIFI-9897
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{InvokeGRPC}} and {{ListenGRPC}} Processors leverage Netty for socket protocol communication, and Netty requires its own [SslContext|https://netty.io/4.1/api/io/netty/handler/ssl/SslContext.html] configuration to support TLS communication.
> The current component implementations require {{nifi-security-utils}}, which includes a dependency on the Bouncy Castle library. Refactoring the Processors to use the Netty [JdkSslContext|https://netty.io/4.1/api/io/netty/handler/ssl/JdkSslContext.html] will enable direct usage of the Java [SSLContext|https://docs.oracle.com/javase/8/docs/api/javax/net/ssl/SSLContext.html] available through the NiFi {{SSLContextService.createContext()}} method. This approach would provide better encapsulation of {{SslContext}} configuration and remove the unnecessary dependency on the Bouncy Castle library in {{nifi-grpc-nar}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)