Blazer Authentication Journey: Exploring Identity and Sign-in Manager

The show discusses setting up Blazor authentication using Identity and Entity Framework with a focus on signin manager implementation.

### Blazor Authentication Journey: Exploring Custom Storage Providers for ASP.NET Core Identity
* 🔐 The Blazor Authentication Journey began in .NET 8 with the realization that enabling authentication in Blazor templates resulted in a **large amount of auto-generated code**, prompting the need to **understand its functionality and customize it**.
* 🛠 To support scenarios like using existing enterprise identity providers (e.g., Azure Active Directory) and avoiding local user storage, the journey focused on **implementing custom storage providers for ASP.NET Core Identity**.
* 📚 The ASP.NET Core Identity documentation serves as a **valuable resource** for understanding and implementing **identity-related functionalities** in Blazor applications.
* 📦 When starting a Blazor project from scratch, the choice of Entity Framework Core (EF Core) storage provider impacts the **generated code and database setup**.
* ⚙ In the Blazor off-from-scratch project, Entity Framework Core was not used, allowing developers to have **full control over the user data storage implementation**.
* 🧑 The `IdentityUser` class provided by ASP.NET Core Identity serves as the base user entity, containing properties such as **`UserName`**, **`Email`**, **`PasswordHash`**, and support for features like **two-factor authentication** and **account lockouts**.
* 📝 The `PersonalData` and `ProtectedPersonalData` attributes can be applied to properties in the `IdentityUser` class to specify the **sensitivity of the data for GDPR compliance and protection**.

### Implementing Custom User Store and Sign-in Manager in Blazor WebAssembly with ASP.NET Core Identity
* 🔒 Implementing a custom user store in ASP.NET Core Identity requires creating a class that implements the **`IUserStore` interface** with a type argument of the **application user class**.
* 🔑 The application user class is a custom implementation of `IdentityUser` that allows you to **store additional user data** alongside the default identity properties like username and email.
* 🔌 Adding the **sign-in manager (`SignInManager`)** to the application enables using convenient methods for user sign-in, such as **`PasswordSignInAsync`**.
* 🏗 While the custom user store implementation provided in the code compiles and runs, it does not perform any **actual user store operations**.
* 🖥 The next step after implementing the user store is to modify the front-end code to use the **sign-in manager** instead of directly calling `HttpContext.SignInAsync`.
* 🤔 Deciding where to place the custom user store class and how to structure the code can be challenging, especially in a **from-scratch Blazor WebAssembly project**.
* 🏷 Naming conventions for folders and classes play a crucial role in making the code **understandable and maintainable**.
* 📈 Understanding and implementing **custom user stores and sign-in managers** in ASP.NET Core Identity is essential for securely managing user authentication and authorization in web applications.

Blazor Authentication - Enabling SignInManager with Custom IUserStore - Part 1

The Dev Talk Show

Discussion on the Blazer Authentication Journey

The hosts discuss the evolution of their show and the different versions of the intro music.

They talk about the busy time at Microsoft and the start of a new phase in the Blazer authentication Journey.

The focus of the journey is on customizing authentication templates and the common patterns of authentication, such as using Microsoft login and Azure Active Directory.

Introducing "Blazor off from Scratch" Repository

The "Blazor off from scratch" repository on GitHub is a resource for those interested in learning how to set up Blazor applications without any authentication.

The repository includes a server project with no interactivity and a WebAssembly version with added authentication, addressing the confusion in Blazor render modes.

The project also covers the process of marshaling user identity from server-side to client-side for WebAssembly, offering a valuable reference for authentication implementation.

Exploring the Use of Signin Manager in ASP.

The "signin manager" method is used for user authentication and requires an implementation of the IUserStore.

The method allows for the setting of persistent cookies and handling of failed login attempts.

NET Core, the use of Signin Manager is essential for user authentication and requires a database implementation, with the option to use SQL Server or local DB for development.

Using Command Line Tools to Interact with Local Databases

Developers can use command line tooling to interact with local databases, allowing them to view, remove, start, and stop instances, which is essential for cleaning up and managing multiple databases effectively.

The default database support differs between command line and Visual Studio, with the command line providing SQL Lite and Visual Studio providing SQL Server, but the switch is possible for simplicity.

By using Entity Framework in Visual Studio, developers have the option to create a DB context based on an application DB context, while the command line tool allows more flexibility and ownership of the code.

NET Core framework comes with built-in features such as username, ID, email, and phone number support, making it essential for user identity management.

The class also includes properties marked as protected personal data, potentially related to GDPR regulations for managing and deleting user data, as well as providing unauthorized access to sensitive information.

The source server in Visual Studio allows for easy navigation and understanding of the platform's implementation, making it a valuable tool for exploring framework classes.

Setting Up Blazor Authentication with Entity Framework

cs sets up the DB context for Blazor identity using Entity Framework.

It specifies the application user and sets the requirement for confirmed accounts.

The setup provides flexibility for customizing account confirmation methods and allows for easy adaptation to new confirmation processes.

The Role of Application User in Managing Sports Teams

Using the Application User allows for additional data to be stored alongside the basic user information in the database.

It provides the flexibility to add custom parameters, such as a team name, which is useful for an application managing sports teams.

The Application User also enables the use of a sign-in manager, providing convenient methods for user authentication and cookie management.

The Sign-In Manager and User Authentication Process

Implementing the sign-in manager is crucial for user authentication and managing claims.

Third-party providers like Google and Microsoft play a significant role in the authentication process, providing necessary claims for user information.

The sign-in manager also raises questions about two-factor authentication and the handling of organizational accounts, adding complexity to the implementation process.

Implementing the Sign-in Manager in Blazor

Learning about the authorized view route component and off provider is necessary for getting the sign-in to work.

The implementation of a user store is crucial before using the sign-in manager, and it requires creating an application user class.

In Blazor, the application user class is not automatically generated, so it needs to be implemented manually, similar to the one in the template.

Creating a New Class and Implementing the Interface

The speaker discusses creating a new class and implementing an interface for the application user.

They also talk about the need to add using statements and the ASP.

The discussion includes plans to modify the code to get the sign-in manager working and the importance of understanding identity in ASP.