โ05-04-2018 09:21 AM
We have configured our Snaplex nodes to run with a customer signed SSL certificate. We use the FQDN in the certificate. The default SnapLogic SSL certificate is not in the JCCโs keystore (jcc.serverkeys.jks). However, when we test the server (Snaplex node) is returning the default SnapLogic SSL certificate to the client during the SSL handshake instead of returning the customer signed SSL certificate. We did some additional investigation and it appears that if the client has the Server Name Indicator (SNI) TLS extension enabled the server selects and returns the default SnapLogic SSL certificate. However, if the SNI TLS extension is disabled the server selects and returns the customer signed SSL certificate thatโs in the JCCโs keystore. We tested the following:
โopenssl s_client -connect node.example.com:8081โ does not use the SNI TLS extension (i.e. server name is not in the client hello message) and the server selects and returns the company signed SSL certificate chain.
โopenssl s_client -connect node.example.com:8081 -servername node.example.comโ uses the SNI TLS extension (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate.
โ./java -Djavax.net.debug=ssl SSLPoke node.example.com 8081โ uses the SNI TLS extension (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate.
โ./java -Djavax.net.debug=ssl -Djsse.enableSNIExtension=false SSLPoke node.example.com 8081โ does not use the SNI TLS extension (i.e. server name is not in the client hello message) and the server selects and returns the company signed SSL certificate chain.
We also tested via browser and curl - they use the SNI TLS extension by default (i.e. server name is in the client hello message) and the server selects and returns the default SnapLogic certificate. I didnโt find a way to disable the extention when using a browser or curl (weโre using version 7.27.0 of curl)
Has anyone else encounter this behavior and been able to resolve it?
โ06-04-2018 05:57 AM
Hi Paul - Did you ever find a solution for this? Iโve been looking into switching out the default self-signed certificates on our groundplex nodes with our own CA-signed certificate, so was curious about this topic.
โ06-04-2018 08:10 AM
Hi Chris - The short answer is โnoโ. I have an open ticket with SnapLogic and our TAM told me that there is a SnapLogic bug, but I donโt know anymore than that at this time. Iโll update this post when I find out more.
โ10-08-2018 09:50 AM
Did you all find a fix for this issue?
โ10-24-2018 06:57 AM
Hi Paul - Did you ever get this resolved? If so, any good lessons learned?