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?
Solved
Corporate SSL Interception
Best answer by aarongundel
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.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
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.