We had a similar issue last year and discovered the following regarding our proxy settings:
- There was a change .NET Core and .NET 5+ to make the platform more agnostic.
- Environment variables http_proxy and https_proxy are now primary and relied upon, instead of WinINet APIs.
- When http_proxy and https_proxy are not defined, .NET will lookup the proxy settings defined for the individual user.
- Proxy settings must explicitly set HTTPS either in environment variable https_proxy or within the User Proxy Settings, otherwise WinINET will default to HTTP.
Before:
proxy.example.com:8080
After:
http = proxy.example.com:8080; https = proxy.example.com:8080
When the “Sign In” button is not working it is a good sign that the request is not being sent via HTTPS. Let us know if the information above helps resolve the issue you are experiencing or if the issue persists along with user proxy settings and/or https_proxy environment value.