Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By : Jürgen Gutsch
Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By: Jürgen Gutsch

Overview of this book

ASP.NET Core is packed full of hidden features for building sophisticated web applications – but if you don’t know how to customize it, you’re not making the most of its capabilities. Customizing ASP.NET Core 6.0 is a book that will teach you all about tweaking the knobs at various layers and take experienced programmers’ skills to a new level. This updated second edition covers the latest features and changes in the .NET 6 LTS version, along with new insights and customization techniques for important topics such as authentication and authorization. You’ll also learn how to work with caches and change the default behavior of ASP.NET Core apps. This book will show you the essential concepts relating to tweaking the framework, such as configuration, dependency injection, routing, action filters, and more. As you progress, you'll be able to create custom solutions that meet the needs of your use case with ASP.NET Core. Later chapters will cover expert techniques and best practices for using the framework for your app development needs, from UI design to hosting. Finally, you'll focus on the new endpoint routing in ASP.NET Core to build custom endpoints and add third-party endpoints to your web apps for processing requests faster. By the end of this book, you'll be able to customize ASP.NET Core to develop better, more robust apps.
Table of Contents (18 chapters)

Securing IdentityManager2

I'm sure you recognized that IdentityManager2 was accessible without a login. This is by design. You need to restrict access to it.

Scott Brady described a way to use IdentityServer to do that (https://www.scottbrady91.com/aspnet-identity/getting-started-with-identitymanager2). We would also propose doing it that way. Setting up IdentityServer isn't that straightforward and isn't covered in this book. Unfortunately, it is not possible to use the default ASP.NET Core individual authentication to protect IdentityManager2. It seems the middleware that creates the IdentityManager2 UI doesn't support individual authentication and redirects to the ASP.NET Core Identity UI.

It would make sense to create a separate ASP.NET Core application that hosts IdentityManager2. This way, this kind of administrative UI would be completely separated from the publicly available application, and you would be able to use either OAuth or Azure Active Directory...