Manuha Vancha
Manuha Vancha
Looks like it's a bug with MSAL broker flow and they just seemed to have fixed it https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/4696 today. Once GCM consumes the latest MSAL, this issue would be fixed.
MSAL [fixed the bug](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/pull/4778) and released a new version [4.61.1](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/blob/main/CHANGELOG.md#4611).
@dscho We tested with the new version `2.5.1` and that unfortunately did not fix our problem. We think it's coming from MSAL and we filed a bug against MSAL [here](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/4858)....
We don’t completely know whether MSAL is causing this issue, so we filed a [bug](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/4858) against MSAL. But we warmed the broker cache successfully with our tool AzureAuth, which is...
It worked!!
Copied the PR to #425 and merged it.
But @kyle-rader-msft wouldn't that be a security issue as it's a plain text?
> Here are some similar issues that might help you. Please check if they can solve your problem. > > * [[Bug] Unable to login with WAM when an app...