On-Premise certificate error about vscode-swaggerhub-release

[hkosova]

This answer suggests adding the trusted certificates (root + intermediate) to the operating system's certificate store:

According to https://code.visualstudio.com/docs/setup/network, the solution is to edit the system certificate store:

Since Chromium uses the OS's certificate trust infrastructure, the preferred option is to add your proxy's certificate to your OS's trust chain.

This means that your answer is OS-dependent:

• Windows: Powershell Import-Certificate or the GUI equivalent
• Mac: Via Keychain Access
• NSS under linux - it is unclear which NSS database it uses. certutil is used to edit them.

Can you try and see if this resolves the issue?

[photchkiss]

Getting the same error. I am wondering if there is a way to provide a cafile or something that includes certificates not signed by a Global CA?

[yondersever]

This answer suggests adding the trusted certificates (root + intermediate) to the operating system's certificate store:

According to https://code.visualstudio.com/docs/setup/network, the solution is to edit the system certificate store:

Since Chromium uses the OS's certificate trust infrastructure, the preferred option is to add your proxy's certificate to your OS's trust chain.

This means that your answer is OS-dependent:

• Windows: Powershell Import-Certificate or the GUI equivalent
• Mac: Via Keychain Access
• NSS under linux - it is unclear which NSS database it uses. certutil is used to edit them.

Can you try and see if this resolves the issue?

It solved my problem.
Thanks for your help.