{"version":"2.1.186","anchor":"proxy-authentication-support-socks","canonical_anchor":"proxy-authentication-support-socks","heading":"Proxy Authentication Support (SOCKS)","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.186\/e\/proxy-authentication-support-socks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.186","markdown":"### Proxy Authentication Support (SOCKS)\n\nThe internal agent proxy now supports authentication credentials when forwarding to an upstream SOCKS proxy.\n\n**Details**\n\n- Auth token is threaded through all proxy environment variables: `HTTP_PROXY`, `HTTPS_PROXY`, `ALL_PROXY`, `GRPC_PROXY`, `FTP_PROXY`, `DOCKER_HTTP_PROXY`, `DOCKER_HTTPS_PROXY`, `CLOUDSDK_PROXY_*`.\n- `GIT_SSH_COMMAND` on Linux includes `proxyauth=srt:${token}` in the socat command.\n- `GIT_CONFIG_PARAMETERS='http.proxyAuthMethod=basic'` is set automatically when a proxy auth token is present.\n- The SOCKS server validates credentials and logs \"SOCKS auth rejected\" on mismatch.\n\n**Evidence**\n\nAuthentication token threading in sandbox environment setup (search for `\"SOCKS auth rejected\"` and `\"GIT_CONFIG_PARAMETERS='http.proxyAuthMethod=basic'\"`)"}