Last merges contained some bad changes

[LXBdev]

Just some quick notes because I just pulled the last version and was unable to use it. Going back to an earlier one for now, may take a look at the issues later.

• B2CPolicyManager.exe.msalcache.bin must not be checked in for the bin folder, it is a system local file and the app will crash on other systems on login
• The new MSAL version fails to login with "no reply urls configured for this app", while the same AAD app still works with the previous ADAL version. Maybe the readme needs to be updated?

@PramodKumarHK89 fyi

[PramodKumarHK89]

@LXBdev : First issue can be handled in the next check in. Regarding the second issue, could you please make sure that, you have the reply url "https://b2capi.com" is present under native platform in your app registration ? (Step number 5 in read me) I understand that, previous worked for you, but there is no change in the code as such which could effect the effect the redirect uri.

ADAL implementation authResult = await ADALIdentityClientApp.AcquireTokenAsync("https://graph.microsoft.com", Properties.Settings.Default.V2AppId, new Uri("https://b2capi.com"), new PlatformParameters(PromptBehavior.Auto));

MSAL implementation

_app = PublicClientApplicationBuilder.Create(Properties.Settings.Default.V2AppId) .WithAuthority(authority) .WithRedirectUri("https://b2capi.com") .Build();

[LXBdev]

@PramodKumarHK89 Thanks for investigating. As a background info: I have a new computer and reused the AAD app from my previous application. I was unable to login. Going back to the previous commit, everything works now. Also if I go to the newest commit now, login works as well. So I am unable to reproduce this at the moment, maybe it will happen again if I use new credentials.

[PramodKumarHK89]

@LXBdev : I tried the app with new registration however, I could not reproduce either. I have created PR by removing the msal cache from bin folder. That should address the first issue.