document proxyEnableKerberosNTLM config (#20162)

* document proxyEnableKerberosNTLM config

* Update content/desktop/settings/windows.md

---------

Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
This commit is contained in:
karman 2024-06-07 14:34:45 +00:00 committed by GitHub
parent b8f407bf3e
commit 57694f21d2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 0 deletions

View File

@ -234,6 +234,10 @@ Kerberos and NTLM proxy authentication are available for Business subscribers wi
Developers are no longer interrupted by prompts for proxy credentials as authentication is centralized. This also reduces the risk of account lockouts due to incorrect sign in attempts.
If your proxy offers multiple authentication schemes in 407(Proxy Authentication Required) response, Docker Desktop selects the strongest authentication scheme (Kerberos, NTLM, Basic, in that order). However, if your Kerberos/NTLM environment is not properly configured, Docker Desktop may fail to authenticate with the proxy, as it will attempt to use the strongest scheme.
To temporarily resolve this issue until your Kerberos/NTLM environment is fixed, you can fallback to the Basic authentication scheme by setting `proxyEnableKerberosNTLM` to `false` in the `settings.json` file located in the `%APPDATA%/Docker/` directory. Quit Docker Desktop and then start it again to effect this change. The `proxyEnableKerberosNTLM` setting is available in Docker Desktop version 4.31 and later.
> **Note**
>
> Docker Desktop also supports the use of [SOCKS5 proxies](../networking.md#socks5-proxy-support).