Description
Can you please explain what issue this sample tries to solve? I adapted the IDP configuration of the sample project to point to a local keycloak instance and was able to log in. The received access token lifetime is 5 minutes. The UI did show the correct claims and returned the weather forecast from the backend.
After the token (+sliding interval) expires the circuit just dies on the 401 returned from the weather forecast backend.
I don't really understand the benefit of the Automatic non-interactive token refresh for an interactive server app.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/blazor-web-app-with-oidc?view=aspnetcore-10.0&pivots=without-yarp-and-aspire-server
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/blazor-web-app-with-oidc.md
Document ID
c3346d3a-346b-8db4-2650-ec044b3f0dd9
Platform Id
1dd51a4e-f734-569f-f6e9-19a27bcd9f4d
Article author
@guardrex
Metadata
- ID: c3346d3a-346b-8db4-2650-ec044b3f0dd9
- PlatformId: 1dd51a4e-f734-569f-f6e9-19a27bcd9f4d
- Service: aspnet-core
- Sub-service: blazor
Related Issues
Description
Can you please explain what issue this sample tries to solve? I adapted the IDP configuration of the sample project to point to a local keycloak instance and was able to log in. The received access token lifetime is 5 minutes. The UI did show the correct claims and returned the weather forecast from the backend.
After the token (+sliding interval) expires the circuit just dies on the 401 returned from the weather forecast backend.
I don't really understand the benefit of the
Automatic non-interactive token refreshfor an interactive server app.Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/blazor-web-app-with-oidc?view=aspnetcore-10.0&pivots=without-yarp-and-aspire-server
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/blazor-web-app-with-oidc.md
Document ID
c3346d3a-346b-8db4-2650-ec044b3f0dd9
Platform Id
1dd51a4e-f734-569f-f6e9-19a27bcd9f4d
Article author
@guardrex
Metadata
Related Issues