Keycload Aspire Client Integration OpenID Blazor sample | Client Secret

[indcoder]

Type of issue

Other (describe below)

Description

The Blazor Sample used as an example in the OpenID is InteractiveServer [ie neither WebAssembly (WASM), nor Auto]

We can then follow the recommended Blazor Backend For Frontend[BFF] pattern for OIDC. and configure the Blazor Interactive Server as a Confidential Client.

This would entail a section describing on configuring the Keycloak client("WeatherWeb") itself

And adding ClientSecret in the Blazor Server's KeyCloakOpenIdConnect configuration.

Also, this would avoid frontchannel exchange of tokens making this a more secure codebase for newbies to adopt as-is.

Page URL

https://learn.microsoft.com/en-us/dotnet/aspire/authentication/keycloak-integration?tabs=dotnet-cli

Content source URL

https://github.com/dotnet/docs-aspire/blob/main/docs/authentication/keycloak-integration.md

Document Version Independent Id

8191aee1-6f2c-5820-046d-17dc81d997e9

Platform Id

5e989b0e-9189-b101-98d3-b5b72245d36b

Article author

@IEvangelist

Related Issues

[indcoder]

cc @IEvangelist I did not know how to categorize this issue type: I went with others. I know it makes the content more complicated and requires a more nuanced review.