You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though redirect_uri is an HTTP URL http://localhost:61886/, we switch the protocol to HTTPS https://localhost:61886/ and visit it in the browser. In the real world, the protocol may be changed by the browser's policy (Azure/azure-cli#10426 (comment)).
Then the browser will show ERR_SSL_PROTOCOL_ERROR:
In the terminal, MSAL shows gibberish characters because these are actually HTTPS-encrypted binary stream.
Expected behavior
MSAL can consider capturing such error and warn the user incorrect protocol is used. I haven't deep dived into the implementation of http.server yet, but it is totally possible that this can't be achieved by MSAL.
The text was updated successfully, but these errors were encountered:
Describe the bug
MSAL shows gibberish (mojibake) if
localhost
is accessed using HTTPS.To Reproduce
Run
The login URL is
Even though
redirect_uri
is an HTTP URLhttp://localhost:61886/
, we switch the protocol to HTTPShttps://localhost:61886/
and visit it in the browser. In the real world, the protocol may be changed by the browser's policy (Azure/azure-cli#10426 (comment)).Then the browser will show
ERR_SSL_PROTOCOL_ERROR
:In the terminal, MSAL shows gibberish characters because these are actually HTTPS-encrypted binary stream.
This issue is reported by Azure/azure-cli#25935, and the solution is Azure/azure-cli#10426 (comment).
Expected behavior
MSAL can consider capturing such error and warn the user incorrect protocol is used. I haven't deep dived into the implementation of
http.server
yet, but it is totally possible that this can't be achieved by MSAL.The text was updated successfully, but these errors were encountered: