This documentation was very helpful. The page suggests that we have full access to configure Identity Server as we see fit. In looking at the overloads for .AddIdentityServer and .AddApiAuthorization in the server project's Startup class, that does seem to be true; however, it would be helpful to provide another section where you demonstrate how to configure an app to support roles or policies -- to support [Authorize(Roles="...")], [Authorize(Policy="...")], <AuthorizeView Roles="...">, <AuthorizeView Policy="...">. Also, it would be helpful to discuss (even at a high-level) how the pattern could be adapted to support a single Blazor WebAssembly app that uses multiple APIs with a single login and multiple Blazor WebAssembly applications that each use a common API.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
This documentation was very helpful. The page suggests that we have full access to configure Identity Server as we see fit. In looking at the overloads for .AddIdentityServer and .AddApiAuthorization in the server project's Startup class, that does seem to be true; however, it would be helpful to provide another section where you demonstrate how to configure an app to support roles or policies -- to support [Authorize(Roles="...")], [Authorize(Policy="...")], <AuthorizeView Roles="...">, <AuthorizeView Policy="...">. Also, it would be helpful to discuss (even at a high-level) how the pattern could be adapted to support a single Blazor WebAssembly app that uses multiple APIs with a single login and multiple Blazor WebAssembly applications that each use a common API.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.