Skip to content

Commit 6704140

Browse files
authored
Add hosting guidance for web farms (#36636)
1 parent 368c3fa commit 6704140

2 files changed

Lines changed: 22 additions & 0 deletions

File tree

aspnetcore/blazor/security/blazor-web-app-with-entra.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Secure an ASP.NET Core Blazor Web App with Microsoft Entra ID
3+
ai-usage: ai-assisted
34
author: guardrex
45
description: Learn how to secure a Blazor Web App with Microsoft Entra ID.
56
monikerRange: '>= aspnetcore-9.0'
@@ -1150,6 +1151,12 @@ Alternatively, use the following `LogInOrOut` component, which doesn't supply a
11501151
11511152
For more information on how this app secures its weather data, see [Secure data in Blazor Web Apps with Interactive Auto rendering](xref:blazor/security/index#secure-data-in-blazor-web-apps-with-interactive-auto-rendering).
11521153
1154+
## Host in a web farm or cluster
1155+
1156+
Server-side Blazor Web Apps hosted in a web farm or cluster of machines must adopt [*session affinity*](xref:blazor/fundamentals/signalr#use-session-affinity-sticky-sessions-for-server-side-web-farm-hosting) to maintain Blazor circuits for users of the app.
1157+
1158+
We also recommend using a shared [Data Protection](xref:security/data-protection/introduction) key ring in production, even when the app uses the Interactive WebAssembly render mode exclusively for client-side rendering (no Blazor circuits).
1159+
11531160
## Troubleshoot
11541161
11551162
[!INCLUDE[](~/blazor/security/includes/troubleshoot-server.md)]
@@ -1164,3 +1171,7 @@ For more information on how this app secures its weather data, see [Secure data
11641171
* [`AuthenticationStateProvider` service](xref:blazor/security/index#authenticationstateprovider-service)
11651172
* [Manage authentication state in Blazor Web Apps](xref:blazor/security/index#manage-authentication-state-in-blazor-web-apps)
11661173
* [Service abstractions in Blazor Web Apps](xref:blazor/call-web-api#service-abstractions-for-web-api-calls)
1174+
* Data Protection resources
1175+
* <xref:security/data-protection/configuration/overview>
1176+
* <xref:security/data-protection/implementation/key-storage-providers>
1177+
* <xref:security/data-protection/implementation/key-encryption-at-rest>

aspnetcore/blazor/security/blazor-web-app-with-oidc.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
22
title: Secure an ASP.NET Core Blazor Web App with OpenID Connect (OIDC)
3+
ai-usage: ai-assisted
34
author: guardrex
45
description: Learn how to secure a Blazor Web App with OpenID Connect (OIDC).
56
monikerRange: '>= aspnetcore-8.0'
@@ -1488,6 +1489,16 @@ The [typed HTTP client](xref:blazor/call-web-api#typed-httpclient) (or [named HT
14881489

14891490
For more information, see the [Duende Access Token Management documentation for Blazor](https://docs.duendesoftware.com/accesstokenmanagement/blazor-server/).
14901491

1492+
## Host in a web farm or cluster
1493+
1494+
Server-side Blazor Web Apps hosted in a web farm or cluster of machines must adopt [*session affinity*](xref:blazor/fundamentals/signalr#use-session-affinity-sticky-sessions-for-server-side-web-farm-hosting) to maintain Blazor circuits for users of the app.
1495+
1496+
We also recommend using a shared [Data Protection](xref:security/data-protection/introduction) key ring in production, even when the app uses the Interactive WebAssembly render mode exclusively for client-side rendering (no Blazor circuits). For more information, see the following articles:
1497+
1498+
* <xref:security/data-protection/configuration/overview>
1499+
* <xref:security/data-protection/implementation/key-storage-providers>
1500+
* <xref:security/data-protection/implementation/key-encryption-at-rest>
1501+
14911502
## Troubleshoot
14921503

14931504
[!INCLUDE[](~/blazor/security/includes/troubleshoot-server.md)]

0 commit comments

Comments
 (0)