Using Microsoft. AspNetCore.Authentication.Cookies

Have you ever wondered how applications let you "Log in with Google" or "Sign in with Microsoft" without asking you to create yet another username and password? In most cases, they use protocols called OAuth and OpenID. Maybe you even heard about SAML or Kerberos, but that is another time... One of the most important things to understand about OAuth is the response type, which is how your authentication information is delivered back to the application after you log in.

In this post, we'll dive into how the Unit of Work and Repository Pattern simplify database access in .NET Core MVC applications. These patterns promote clean architecture, reusability, and a clear separation of concerns. Let's explore their implementation through an example using BaseService, GenericRepository, and UnitOfWork with a UserMasterService. Why Use the Repository and Unit of Work Pattern? Repository Pattern: Encapsulates data access logic, keeping it clean and isolated.

Introduction Umbraco is a popular CMS that offers extensive customization and security features. One of the critical aspects of managing an Umbraco site is ensuring that only authenticated users can access certain parts of the site. In this guide, we'll create an accessor to check the user's authentication status in the Umbraco backoffice and use it in a view to conditionally display content. Prerequisites Basic knowledge of ASP.NET Core. An existing Umbraco installation.