It seems there is no programming in the openidconnect authentication for asp.net core to manage the access_token on the server after received. I found that I can intercept the cookie validation event and check if the access token has expired. If so, make a manual HTTP call to the token endpoint with the grant_type=refresh_token. By … Read more
I also had this issue. “Add Controller>API Controller with actions, using Entity Framework” would give the “Package Restore Failed” error. As Anish stated, it seems to be due to package versions being mis-aligned. I was able to resolve this issue using “Manage NUGET Packages for Solution”, then performing an “Update All”. This set my AspNetCore … Read more
You can use the Quartz.Spi.IJobFactory interface and implement it. The Quartz documentations states: When a trigger fires, the Job it is associated to is instantiated via the JobFactory configured on the Scheduler. The default JobFactory simply activates a new instance of the job class. You may want to create your own implementation of JobFactory to … Read more
There’s a problem to your approach: .NET Standard is the most bare-bones implementation of .NET available, meaning that only basic features which are platform- and scenario-agnostic are implemented. HttpContext exists on both the .NET Framework and .NET Core (both of which implement .NET Standard, by the way), but being specific to the Web, it does … Read more
Never mind, the code is here public async Task Invoke(HttpContext context) { var watch = new Stopwatch(); watch.Start(); //To add Headers AFTER everything you need to do this context.Response.OnStarting(state => { var httpContext = (HttpContext)state; httpContext.Response.Headers.Add(“X-Response-Time-Milliseconds”, new[] { watch.ElapsedMilliseconds.ToString() }); return Task.CompletedTask; }, context); await _next(context); }
Not the way you want; policies are designed to be cumulative. For example if you use two separate attributes then they must both pass. You have to evaluate OR conditions within a single policy. But you don’t have to code it as ORs within a single handler. You can have a requirement which has more … Read more
This usually happens in the _LoginPartial.cshtml or _ManageNav.cshtml razor view. Eg. @inject UserManager<IdentityUser> userManager Must be changed to @inject UserManager<MyUserStore> userManager The same applies to SignInManager. When registering your own MyUserStore (bad name, should be MyUser) for the AspNetCore Identity, the UserManager<> type will be registered to the ServiceCollection as UserManager<MyUserStore>. Whenever you want to … Read more
For me the problem was solved by closing down Visual Studio, deleting project.lock.json and starting Visual Studio again. Edit: I was using RC1.
IHttpContextAccessor is no longer wired up by default, you have to register it yourself services.TryAddSingleton<IHttpContextAccessor, HttpContextAccessor>();