You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2016/10/26 14:09:58 UTC
[jira] [Assigned] (CAMEL-10341) When using SSL, a NettyConsumer set
to Client Mode does not initiate a handshake
[ https://issues.apache.org/jira/browse/CAMEL-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Cosentino reassigned CAMEL-10341:
----------------------------------------
Assignee: Andrea Cosentino
> When using SSL, a NettyConsumer set to Client Mode does not initiate a handshake
> --------------------------------------------------------------------------------
>
> Key: CAMEL-10341
> URL: https://issues.apache.org/jira/browse/CAMEL-10341
> Project: Camel
> Issue Type: Bug
> Components: camel-netty4
> Affects Versions: 2.17.1, 2.17.2, 2.17.3
> Reporter: Matt Shaw
> Assignee: Andrea Cosentino
> Fix For: 2.17.4
>
> Attachments: 0001-Added-fix-for-SSL-Consumer-in-Client-Mode-not-initia.patch
>
>
> When used as a Consumer Netty can be put into {{clientMode}}, which will cause it to act as a client rather than a server. However when SSL is enabled on the endpoint the SSL Handshake does not occur.
> {{DefaultServerInitializerFactory}} creates a new {{SslHandler}} on-demand during channel initialisation, but forces the {{SSLEngine}} to _not_ use client mode, regardless of the setting in the {{NettyConfiguration}} instance.
> To cause handshakes to happen when in client mode, set the section in {{DefaultServerInitializerFactory.configureServerSSLOnDemand()}} to:
> {code}
> SSLEngine engine = sslContext.createSSLEngine();
> engine.setUseClientMode(consumer.getConfiguration().isClientMode());
> engine.setNeedClientAuth(consumer.getConfiguration().isNeedClientAuth());
> {code}
> For reference see [StackOverflow|http://stackoverflow.com/q/39574656/218597].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)