[CAMEL-16830] Use GrpcSslContexts.configure for gRPC producer sslContext configuration

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.12.0
• Component/s: camel-grpc
• Estimated Complexity: Unknown
• Assignee: James Netherton
• Reporter: James Netherton
• Created: 30/Jul/21 15:07
• Updated: 03/Aug/21 07:05
• Resolved: 03/Aug/21 07:05

Description

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.

Issue Links

• links to: GitHub Pull Request #5912