Copy link to clipboard
Copied
I noticed that CEF honors the OS truststore, as it properly loads, e.g., img when I added a selfsign CA to the OS truststore.
However, this is not the case with Axios queries. In this case, I had to explicitly add the CA in the https.Agent to make it work. Axios documentation seems to say that it should also be using the OS truststore, but I haven't tried this in the normal Nodejs environment.
I'm asking as it's a bit awkward to make the user both 1) add CA to the truststore and 2) add the CA so it can be read by the extension. It would be nice if the internal Node could use the same truststore as CEF uses.
Any thoughts on this? TIA.
Here's the only information we have, on using Node.js in a panel:
https://blog.developer.adobe.com/how-to-build-a-node-js-server-in-a-panel-ba1d63ea67e2
Also potentially helpful:
https://stackoverflow.com/questions/49655154/access-node-in-adobe-cep-extension
Copy link to clipboard
Copied
Here's the only information we have, on using Node.js in a panel:
https://blog.developer.adobe.com/how-to-build-a-node-js-server-in-a-panel-ba1d63ea67e2
Also potentially helpful:
https://stackoverflow.com/questions/49655154/access-node-in-adobe-cep-extension
Copy link to clipboard
Copied
I've already managed to enable and use Node properly in CEP such that I was able to utilize the Axios library for making external API calls. However, when adding HTTPS support to it, CEP Node wouldn't use the OS trust store, as it would in a normal Node environment. The question is whether it is also possible for CEP Node to do that.