Analyze Blazor WebAssembly app with feature toggles - #1
Open
rfalanga wants to merge 1 commit into
Open
Conversation
This document provides an analysis of a hosted Blazor WebAssembly app demonstrating feature toggles with authenticated API access, detailing its structure, functionality, and implementation.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This document provides an analysis of a hosted Blazor WebAssembly app demonstrating feature toggles with authenticated API access, detailing its structure, functionality, and implementation.
This is from this repo on Feature Flags
I asked GitHub Copilot if it was necessary to use Microsoft Entra ID/Azure AD to run this application. In short, it said yes. Here is its full answer:
No—not strictly to start the process, but yes for the app’s intended behavior as implemented.
• The server is wired to Entra auth in Server/Program.cs via AddMicrosoftIdentityWebAppAuthentication(...).
• Sign-in/sign-out endpoints are Entra/OpenID Connect based in Server/Controllers/AccountController.cs.
• Protected APIs require authenticated cookies (for example DirectApiController, FeatureXApiController, GraphApiCallsController).
• Graph functionality specifically depends on Entra-issued tokens/scopes (User.ReadBasic.All user.read).
So, as-is, you can launch it, but to actually authenticate and use secured/API features, you need a valid Microsoft Entra ID app registration and tenant config.