Single Sign-on Authentication and authorization in ASP.NET Core.png

sso.tar.gz

Stand Alone Auth Provider

Client App Only

Full Authentication Flow

Full Authentication Flow With Secondary App

Blazor WebAssembly OIDC

Client and back-end

Securing web applications is extremely important, as you do not want unauthorized people to gain access to your data. The most convenient way of securing an application is to use single sign-on (SSO) because it allows users to authenticate once and gain access to all apps within the same system.

In this course, you’ll cover the process of using SSO in ASP.NET Core apps. You’ll also cover its usage inside all application types supported by ASP.NET Core, including MVC, web API, gRPC services, Blazor, and SignalR.

By the end of this course, you will have learned what SSO consists of, what protocols it uses, and how it’s configured inside an ASP.NET Core middleware. You will also have learned how to secure any endpoints, pages, and views supported by ASP.NET Core.

Using Single Sign-On for Securing Applications in ASP.NET Core

Blazor Server runs directly in the browser.

Blazor WebAssembly runs directly in the browser.

Blazor Server is a standard .NET web application that servers Razor components to the browser in the form of HTML.

Blazor server uses the `.cshtml` extension for Razor components.

**(Select all that apply.)** What are the differences between Blazor WebAssembly and Blazor Server? 

(Select all that apply.) What are the differences between Blazor WebAssembly and Blazor Server?

Which typical OIDC authentication setting cannot be applied in Blazor WebAssembly?

Which typical OIDC authentication setting cannot be applied in Blazor WebAssembly?

Because a Razor component is just a component, such a requirement cannot be configured on a per-component basis.

By adding the `[Authorize]` attribute to the Razor Page that hosts the Razor component

By adding the `[Authorize]` attribute to the Razor component via the `@attribute` keyword

By adding the `RequireAuthorization()` invocation to the `MapBlazorHub()` method

How can authorization requirements be configured inside an individual Razor component?

How can authorization requirements be configured inside an individual Razor component?

You must have two separate Razor components: one for the registered users and one for unregistered users.

By using the `AuthorizeView` with the `Authorized` and `NotAuthorized` sub-views

By using the `AuthorizeRouteView` with the `Authorized` and `NotAuthorized` sub-views

By having a mixture of the `[Authorize]` and `[AllowAnonymous]` attributes inside a Razor component

What needs to be done in a Blazor component if you want to hide some content from unregistered users and instead display different content to them?

What needs to be done in a Blazor component if you want to hide some content from unregistered users and instead display different content to them?

Add the `RequireAuthorization()` invocation on the `MapBlazorHub()` method.

Add the `RequireAuthorization()` invocation on the `MapRazorPages()` method.

Apply the `AuthorizeRouteView` component in the `App.razor` file.

Apply the `AuthorizeView` to the application layout.

What should be done if you want to force a Razor Server application to initiate the OIDC authentication flow for anonymous users by default?

What should be done if you want to force a Razor Server application to initiate the OIDC authentication flow for anonymous users by default?

Test your knowledge of enabling SSO in Blazor applications.

Introduction to Single Sign-On (SSO)

JWT and Authorization Middleware

Enabling SSO in MVC Apps

Enabling SSO in Razor Pages

Enabling SSO in Web API

Enabling SSO in Blazor

Enabling SSO in gRPC

Enabling SSO in SignalR

Wrapping Up

Appendix

Quiz Yourself on SSO in Blazor