What problem does it solve? Migrating authentication and authorization from ASP.NET MVC (Windows Auth, Forms Auth, ASP.NET Identity) to a Node.js API plus React frontend is error-prone, with risks like token audience mismatches, lost AD group mappings, and insecure cookie handling. This Skill provides decision matrices, templates, and checklists to move to Microsoft Entra ID, OIDC, and JWT safely. ## Core Features & Use Cases - Source-to-target decision matrix: Maps Windows Auth, Forms Auth, ASP.NET Identity, Basic Auth, and SAML to Entra ID, JWT bearer tokens, or BFF cookie sessions. - Ready-to-use templates: Includes MSAL React provider and route guards, framework-agnostic jose token validation middleware, a Passport passport-azure-ad strategy, and a PowerShell script that bootstraps Entra app registrations with GitHub Actions OIDC federated credentials. - Authorization mapping guidance: Converts [Authorize], [AllowAnonymous], and IsInRole checks into requireAuth, requireRole, and requireAnyRole middleware, with AD group-to-Entra group Object ID and App Roles strategies. - Use Case: When migrating an MVC app that uses [Authorize(Roles = "Admin")] and AD group checks, use this Skill to configure Entra app roles, wire MSAL into React, and enforce role claims in the Node API. ## Quick Start Ask the AI to migrate the ASP.NET MVC Windows Authentication and [Authorize] attributes in your controllers to Entra ID JWT validation in the Node.js API with MSAL sign-in in the React frontend.
