Revert section removal in Blazor WASM migration (#20677)

pull/20678/head
Luke Latham 2020-11-19 11:42:56 -06:00 committed by GitHub
parent 43a82cdd22
commit 242c36025c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 1 deletions

View File

@ -4,7 +4,7 @@ author: scottaddie
description: Learn how to migrate an ASP.NET Core 3.1 project to ASP.NET Core 5.0.
ms.author: scaddie
ms.custom: mvc
ms.date: 11/18/2020
ms.date: 11/19/2020
no-loc: [appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
uid: migration/31-to-50
---
@ -445,6 +445,23 @@ For a standalone Blazor WebAssembly app registered in the Azure portal to use Az
For more information, see <xref:blazor/security/webassembly/standalone-with-azure-active-directory-b2c>.
### Hosted Blazor WebAssembly app with Azure Active Directory (AAD) or AAD B2C
Follow the guidance in the preceding [Update Blazor WebAssembly and Blazor Server projects](#update-blazor-webassembly-and-blazor-server-projects) and [Update Blazor WebAssembly projects](#update-blazor-webassembly-projects) sections.
The *`Client`* app registration of a hosted Blazor solution that uses AAD or AAD B2C for user authentication should use a **Single-page application** Azure Apps platform configuration.
In the Azure portal *`Client`* app registration **Authentication** blade:
1. Remove the **Web** platform configuration.
1. Add a **Single-page application** platform configuration with the app's redirect URI.
1. Disable **Implicit grant** for **Access tokens** and **ID tokens**.
For more information, see:
* <xref:blazor/security/webassembly/hosted-with-azure-active-directory>
* <xref:blazor/security/webassembly/hosted-with-azure-active-directory-b2c>
### Update the Server project of a hosted Blazor solution
Follow the guidance in the preceding sections: