Proxy configuration for Snyk CLI
When you use the Snyk CLI behind a proxy, you must provide the proxy configuration by using the following environment variables:
HTTPS_PROXYmeans that requests using
httpsprotocol use this proxy. The proxy itself does not need to use
By default Snyk CLI tries to detect and apply proxy authentication.
If the proxy server requests proxy authentication (as indicated by a
PROXY-AUTHENTICATEresponse header), and both server and CLI support the same authentication mechanism, the CLI authenticates as the user who is currently logged in to the operating system (SSO).
This is supported for the following authentication mechanism:
- Kerberos (on all OS)
- NTLM (Windows NT LAN Manager)
On Windows operating systems (OS), the Kerberos and NTLM authentication mechanisms are provided by the OS itself and available for all domain users.
Snyk CLI does not require any specific configuration.
On non-Windows operating systems, Snyk CLI also supports SSO but, in addition, must be configured with the following environment variables.
KRB5_CONFIG # default "/etc/krb5.conf"
KRB5CCNAME # default "FILE:/tmp/krb5cc_<UserUID>"
The use of these variables follows the MIT Kerberos implementation:
To disable authentication, specify the following command line parameter:
If you have connection problems, enable debug output
-dfor helpful insights.