I'm developing an ASP.NET Core application with a Vue.js frontend, and I'm trying to implement SignalR for real-time notifications. However, I'm encountering a CORS issue when attempting to connect to my SignalR hub. Below are the details of my setup…
I'm wondering what component verifies a incoming authentication-cookie and sets HttpContext.User.Identity.IsAuthenticated to true even before the very first middleware component is executed, even when I do not have app.UseAuthentication()in the middleware pipeline at all. So far, I expected this authentication…
I have two ASP.NET MVC applications with session configurations. When I log in from app1, that login is successful. After logging in from app2, it overwrites app1's session cookie and successfully logs in app2. But refreshing the app1 result redirects…
im using JWT to Authentication, and I'm storing it in Cookies. I want to use HttpContext.SignInAsync to login, I saw a lot of example with basic Cookie Auth, but not with JWT. Here is my Startup.cs services.AddTransient<IUserRepository, UserRepository>(); services.AddTransient<ITokenService, TokenService>();…
I have a .NET Core 3 project (recently upgraded from 2.2) that uses a Redis distributed cache and cookie authentication. It currently looks something like this: public void ConfigureServices(IServiceCollection services) { // Set up Redis distributed cache services.AddStackExchangeRedisCache(...); ... services.ConfigureApplicationCookie(options…