• EN
Solved

Corporate SSL Interception

  • 26 October 2017
  • 1 reply
  • 7 views
A
Badge

I have a problem in FME Desktop 2017.1. My company uses a custom certificate authority to monitor TLS traffic. In Desktop 2016, I was able to modify the cacert keystore in $FME_HOME\\jre\\lib\\security\\cacerts and add our root cert. After that FME viewed our custom CA as trusted. In 2017.1, that does not seem to be the case. I went through the same procedure and added the cert to that keystore - but 2017.1 no longer appears to respect that keystore (or the windows system root certificates, where it is also installed and fully trusted). Did something change in 2017.1? Am I missing anything obvious?

icon

Best answer by aarongundel 27 October 2017, 17:25

View original

1 reply

A
Badge

This turned out to be an issue related to the VM I was running Desktop on. I was using a NAT'd connection to the host machine. When I switched over to use bridged internet, things started working again. My best guess here is that the NAT box broke the trust chain somehow. Anyway, I'm able to work around it now.

Reply


Community Stats

28,807
Posts
109,806
Replies
36,622
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.