-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Issue with MSAL 4.16.0 library when using Integrated Windows Authentication #1988
Comments
I think you are using some sort of federation and the federated server is refusing the connection. Are you maybe behind a proxy that requires auth?
It migth help to capture the traffic using Fiddler/ |
I am not behind any proxy actually. This works fine when I use MSAL 4.15.0. (The same code that I showed). I am trying to understand what is going wrong here. |
We started receiving this error randomly beginning around Saturday and we didn't change what was in production. Its the reason why I submitted PR #1984 so hopefully I can figure out what's going on. Not having the body is an issue. We are unfederated with Seamless SSO. |
@jabbera - we plan to release MSAL 4.18 end of next week, but I've built a preview package that has your change - see attached (I had to rename to zip, but it's a nupkg). |
Thanks! |
I have had the same error with 4.17.1 when upgrading from 4.6.0 where the exact same code was working.
|
I am experiencing the same issue on MSAL 4.17.1 But I only see the issue on .NET core (3.1), if i run the exact same code on .NET framework (4.7.2) - it works as intended If I downgrade MSAL to v. 4.15 the token acquisition works as intended |
Was able to reproduce. Investigating solution |
I have noticed the same change in behavior for AcquireTokenByIntegratedWindowsAuth when switching from Microsoft.Identity.Client version 4.15.0 to any of the newer versions. 4.15.0 is the last package version where my code works with AcquireTokenByIntegratedWindowsAuth. Older versions work too. As soon as I switch to 4.16.0 up to 4.18.0 (most recent version at the time I write this) the parsing_wstrust_response_failed error is thrown. This is for an application on .Net Core 3.1. |
This is the root cause: dotnet/runtime#26397 i.e. UseDefaultCredentials is broken. |
Which Version of MSAL are you using ?
MSAL 4.16.0
Platform
netcore
What authentication flow has the issue?
Other? - please describe;
Is this a new or existing app?
c. This is a new app or experiment
Repro
The exception I get is shown below
Expected behavior
Expected to write access token onto the console.
Actual behavior
Below is the exception that occurs
Additional context/ Logs / Screenshots
Point to note here is that when I use MSAL 4.15.0 or below version, it works fine. It only happens from MSAL 4.16.0 and above versions.
The text was updated successfully, but these errors were encountered: