bwfc-identity-migration

# Web Forms Identity → Blazor Identity Migration This skill covers migrating ASP.NET Web Forms authentication (Identity, Membership, FormsAuthentication) to Blazor Server using ASP.NET Core Identity. **Related skills:** - `/bwfc-migration` — Core markup migration (controls, expressions, layouts) - `/bwfc-data-migration` — EF6 → EF Core, data access, architecture decisions --- ## Overview Web Forms authentication typically uses one of three systems. The migration path depends on which one: | Web Forms Auth System | Era | Blazor Migration Path | |----------------------|-----|----------------------| | ASP.NET Identity (OWIN) | 2013+ | ASP.NET Core Identity (closest match) | | ASP.NET Membership | 2005-2013 | ASP.NET Core Identity (schema migration required) | | FormsAuthentication | 2002-2005 | ASP.NET Core Identity or cookie auth | --- ## ⚠️ Cookie Auth Under Interactive Server Mode > **CRITICAL:** When using `<Routes @rendermode="InteractiveServer" />` (global interactive server mode), `HttpContext` is **NULL** during WebSocket circuits. This means cookie-based authentication operations — login, register, logout — **cannot** be performed via Blazor component event handlers (e.g., `@onclick`). They will silently fail: no exception is thrown, but no cookie is set. **Why this happens:** After the initial HTTP request, Blazor Server communicates over a WebSocket (SignalR circuit). There is no HTTP response to attach a `Set-Cookie` header to. `SignInAsync()` called inside...