Closed jabbera closed 4 years ago
@trwalke : hoping you can review/investigate this issue.
Never mind.
What a hot mess this issue is but turns out it's on our firewall. Will update more when I have details.
Turns our our firewall was intercepting the repsonse
Reopening the issue so that we can capture the supportability fix that you've done in the release notes @jabbera
Which Version of MSAL are you using ? 4.13.0
Platform net462
What authentication flow has the issue?
Other? - please describe;
Is this a new or existing app? This is a test app
Repro
Expected behavior A clear and concise description of what you expected to happen (or code). Seamless SSO works.
Actual behavior Exception is thrown even without my logging handler:
{"Federated service at https://autologon.microsoftazuread-sso.com/SNIP/winauth/trust/2005/windowstransport?client-request-id= returned error: "}
For some reason https://autologon.microsoftazuread-sso.com//winauth/trust/2005/windowstransport?client-request-id= is returning a 401 and the request is not attaching my kerberos token or resending witht he token after a 401. SSMS and chrome are working fine with seamless SSO.
Request with headers:
Response with headers: