Closed FreeSMIME closed 4 years ago
Hi @FreeSMIME, I am sorry about your troubles.
You are right on your statement about calling TokenAcquisition.AddAccountToCacheFromAuthorizationCodeAsync(...)
in order to populate the token cache. This is the entry point for the caching logic.
About the ASP.NET Core 3.0 problem, I think @jmprieur will be the best person to help you.
@FreeSMIME : It's on the backlog to update the samples (and also MSAL.NET, BTW) to .NET Core 3.0.
Any idea on when these will be migrated to 3.0?
We are working on it For the ASP.NET Core Web API tutorial, we already have a PR. https://github.com/Azure-Samples/active-directory-dotnet-native-aspnetcore-v2/pull/111 I hope to get to this for the ASP.NET Core Web app today and the .NET daemon core daemon app calling its own Web API today (will be the same code for Microsoft.Identity.Web btw)
@jmprieur looks like the PR was merged. Is it safe to say the current build works with .NET Core 3.0?
@jasonshave : the ASP.NET Core Web API tutorial (for which the PR got merged) is ready. The ASP.NET Core Web app needs a bit more work. On it (intermittently as I also have other things to do)
Done
This issue is for a: (mark with an
x
)The issue was found for the following scenario:
I am using Razor Pages and need to get the client authentication working and the following doesn't seem to log any middleware events
It seems that I need to call TokenAcquisition.AddAccountToCacheFromAuthorizationCodeAsync(...
... in order to populate the MSAL cache to it can be used with the OBO flow. But until then, I'm stuck.
Any suggestions on how to proceed with making Microsoft.Identity.Web work with Core 3?
(I wasn't sure what kind of project to use with Core 3, so I just dragged the files into the WebApp under the infrastructure directory. Better suggestions appreciated too. TY