From 0d08af414a3621430e653b14c68aed3fd8da9f1a Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 26 May 2021 13:41:54 -0500 Subject: [PATCH] Improve Blazor security NOTE --- aspnetcore/blazor/security/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/aspnetcore/blazor/security/index.md b/aspnetcore/blazor/security/index.md index 623009ec7594..73e05fe5c882 100644 --- a/aspnetcore/blazor/security/index.md +++ b/aspnetcore/blazor/security/index.md @@ -23,7 +23,10 @@ Blazor WebAssembly apps run on the client. Authorization is *only* used to deter [Razor Pages authorization conventions](xref:security/authorization/razor-pages-authorization) don't apply to routable Razor components. If a non-routable Razor component is [embedded in a page](xref:blazor/components/prerendering-and-integration), the page's authorization conventions indirectly affect the Razor component along with the rest of the page's content. > [!NOTE] -> and aren't supported in Razor components. +> and aren't supported in Razor components. Blazor Server apps use ASP.NET Core Identity. For more information, see the following guidance: +> +> * +> * [Scaffold ASP.NET Core Identity into a Blazor Server app without existing authorization](xref:security/authentication/scaffold-identity#scaffold-identity-into-a-blazor-server-project-without-existing-authorization) ## Authentication