|Email Plug-in (Reporting):||22.214.171.124|
|Email Plug-in (Encryption):||126.96.36.199|
We're enforcing TLS on the outbound with an external party (let's call it: external.com). The certificate they (external.com) use to do the TLS is signed by their own sub-CA, and neither it, neither the Root CA are recognized by default on ESA.
So, if we configure to do TLS VERIFIED, it fails.
The question is, is it possible to import their (external.com) sub-CA and Root CA certificates so, our ESA can VERIFY the TLS connection with this external party?
Thanks a lot for your help!
Solved! Go to Solution.
If I understood it well, this custom list, each time we add a new certificate of a external party root/sub CA we need to import the full list, right? It means, export the custom list include the new ones and then import. Am I right? Thanks!!
If I understood it well, this custom list, each time anyone wants to add a new certificate of a external party root/sub CA it is needed to import the full list, right? It means: export the custom existent list, add the new ones to that list, and then import this list. Am I right? Thanks!!