[ https://issues.apache.org/jira/browse/CAMEL-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518493#comment-15518493 ]
Claus Ibsen commented on CAMEL-10341: ------------------------------------- Are you able to work on a patch / github PR with a fix for this? > 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 > Fix For: 2.17.4 > > > 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)