You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some pretty awesome security software that does this man-in-the-middle-attack TLS interception where it decrypts and re-encrypts all TLS traffic.
For Node apps, I've been able to add the environment variable NODE_EXTRA_CA_CERTS and point it to the security software certificate.
It doesn't seem that this obeys that construct, or perhaps the environment in VS Code extensions isn't seeing that value propagated down? I'm encountering issues while trying to use the Azure Pipelines Language Server that uses this library. It pretty consistently issues a message like: "Error: Unable to get local issuer certificate" and that generally points at this MitM thing.
The text was updated successfully, but these errors were encountered:
We have some pretty awesome security software that does this
man-in-the-middle-attackTLS interception where it decrypts and re-encrypts all TLS traffic.For Node apps, I've been able to add the environment variable
NODE_EXTRA_CA_CERTS
and point it to the security software certificate.It doesn't seem that this obeys that construct, or perhaps the environment in VS Code extensions isn't seeing that value propagated down? I'm encountering issues while trying to use the Azure Pipelines Language Server that uses this library. It pretty consistently issues a message like: "Error: Unable to get local issuer certificate" and that generally points at this MitM thing.
The text was updated successfully, but these errors were encountered: