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 a ProGet Server running internal, which we use to host our private packages but also to mirror the official npm registry. This ProGet Server uses a certificate trusted by our own local ca.
NPM works fine with our custom cert but "ng update" seems to ignore out ca settings.
"ng update" works fine with strict-ssl disabled, but this is not a solution that meets our internal security ruling.
Uh oh!
There was an error while loading. Please reload this page.
We have a ProGet Server running internal, which we use to host our private packages but also to mirror the official npm registry. This ProGet Server uses a certificate trusted by our own local ca.
NPM works fine with our custom cert but "ng update" seems to ignore out ca settings.
"ng update" works fine with strict-ssl disabled, but this is not a solution that meets our internal security ruling.
Versions
Repro steps
You need a npm repository with an custom certificate.
npm config set registry https://proget.xxx.com/npm/repo
npm config set cafile "C:\\XXX.cer"
ornpm config set ca "BASE64 CERT"
ng update
Observed behavior
Desired behavior
Mention any other details that might be useful (optional)
ng update
works fine without the custom registry.The text was updated successfully, but these errors were encountered: