You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2021/07/30 15:08:00 UTC
[jira] [Created] (CAMEL-16830) Use GrpcSslContexts.configure for
gRPC producer sslContext configuration
James Netherton created CAMEL-16830:
---------------------------------------
Summary: Use GrpcSslContexts.configure for gRPC producer sslContext configuration
Key: CAMEL-16830
URL: https://issues.apache.org/jira/browse/CAMEL-16830
Project: Camel
Issue Type: Improvement
Components: camel-grpc
Reporter: James Netherton
Assignee: James Netherton
Fix For: 3.12.0
I noticed there's a subtle difference in the way that the gRPC consumer and producer do the configuration for TLS support.
The consumer does:
serverBuilder = serverBuilder.sslContext(GrpcSslContexts.configure(sslContextBuilder).build());
Where as the producer does:
channelBuilder = channelBuilder.sslContext(sslContextBuilder.build());
GrpcSslContexts has some useful internal logic which can do fallback if the specified security provider is not available. So we should use it on the producer side.
My main motivation for this is for Camel Quarkus where there is no native mode support for Netty + OpenSSL, so the fallback mechanism becomes very useful.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)