04-24-2019 03:08 AM - edited 04-24-2019 03:09 AM
Hi,
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!
Best Regards,
Jesús.
Solved! Go to Solution.
04-24-2019 07:52 AM
04-24-2019 07:52 AM
04-24-2019 08:05 AM
04-24-2019 08:11 AM
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!!
04-24-2019 08:31 AM
04-25-2019 12:51 AM
Thanks for your response.
04-24-2019 08:13 AM
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!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide