A hands-on workshop for learning ASP.NET Core Authorization through step-by-step labs covering policies, roles, claims, and resource-based authorization.
AspNetAuthorizationWorkshop is a hands-on lab designed to teach developers how to implement authorization in ASP.NET Core applications. It walks through key concepts like policies, roles, claims, and resource-based authorization with step-by-step exercises. The workshop helps developers secure their applications by understanding and applying ASP.NET Core's authorization framework.
ASP.NET Core developers who need to implement authentication and authorization in their applications, particularly those new to ASP.NET Core's authorization system or upgrading from older versions.
It provides a practical, guided approach to learning authorization with real code examples, covering everything from basic setup to advanced scenarios like custom policies and resource-based checks, all updated for ASP.NET Core 2.1.
A workshop for moving through the various new pieces in ASP.NET Core Authorization
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides incremental exercises from basic authentication to advanced authorization scenarios, such as resource-based checks and multiple handlers, ensuring gradual learning with practical code examples.
Guides through defining and using authorization policies with custom requirements and handlers, based on real code from the README, like the MinimumAgeRequirement and OfficeEntryRequirement.
Includes examples for securing specific resources, such as the Document class, showing how to integrate authorization with business logic in controllers and views.
Explains role-based, claim-based, and policy-based authorization with clear examples, helping developers understand ASP.NET Core's authorization framework thoroughly.
Targeted at ASP.NET Core 2.1 and Visual Studio 2017, which are obsolete; modern versions have significant changes, and the code may not work without adaptation.
Requires creating projects, adding code step-by-step, and managing dependencies manually, as shown in the preparation steps, which can be cumbersome for quick learning or reference.
Primarily uses cookie-based authentication with fake user principals, lacking coverage of modern methods like JWT or OAuth, which are common in APIs and cloud-based apps.
Focuses on the MVC template and patterns, which might not align with developers using newer ASP.NET Core architectures like Razor Pages or minimal APIs.