Migrate ASP.NET Web Forms Identity and Membership authentication to Blazor Server Identity. Covers OWIN to ASP.NET Core middleware, login page migration, BWFC login controls, role-based authorization, and cookie auth under Interactive Server mode. WHEN: "migrate identity", "login page migration", "OWIN to core", "cookie auth blazor", "LoginView migration".
87
82%
Does it follow best practices?
Impact
96%
1.15xAverage score across 3 eval scenarios
Passed
No known issues
Cookie auth via HTTP endpoints
HTTP form submission
100%
100%
Minimal API endpoint
100%
100%
DisableAntiforgery called
100%
100%
Register uses HTTP form
100%
100%
Register endpoint DisableAntiforgery
100%
100%
Endpoint redirects after auth
100%
100%
No SignInAsync in component
100%
100%
WebSocket/HttpContext explanation
100%
100%
Logout uses POST form
75%
50%
AddCascadingAuthenticationState
0%
100%
BWFC login controls and LoginView migration
BWFC LoginView used
100%
100%
AnonymousTemplate preserved
100%
100%
LoggedInTemplate preserved
100%
100%
BWFC LoginName used
100%
100%
BWFC LoginStatus used
100%
0%
AuthorizeView for role group
0%
100%
AddBlazorWebFormsComponents registered
0%
100%
AddCascadingAuthenticationState registered
0%
100%
LoginView not replaced with AuthorizeView
100%
100%
No AuthorizeView for main content
100%
100%
Auth state access and role-based authorization
No HttpContext.Current
100%
100%
No OWIN context calls
100%
100%
AuthStateProvider or CascadingParameter
100%
100%
Async auth state retrieval
100%
100%
UserName from auth state
100%
100%
Role check from auth state
100%
100%
AccountDashboard Authorize attribute
100%
100%
AdminPanel Authorize with role
100%
100%
Migration notes explain HttpContext
100%
100%
Web.config rules not used
100%
100%
9bf8669
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.