Repository navigation
fix(identitylab): use authenticated HTTP context for Blazor management operations - #154
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #154 +/- ##
=======================================
Coverage 87.20% 87.21%
=======================================
Files 580 580
Lines 18915 18915
Branches 2228 2228
=======================================
+ Hits 16495 16496 +1
+ Misses 1617 1616 -1
Partials 803 803
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
mckaragoz
added a commit
that referenced
this pull request
Nov 9, 2026
* Refine deploy condition in GitHub Actions workflow * Update GitHub Workflows Update GitHub Workflows * fix(identitylab): use authenticated HTTP context for Blazor management operations (#154) * fix(identitylab): use authenticated HTTP context for Blazor management operations * fix(identitylab): pass validated request flow explicitly to rollback
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
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.
Interactive Blazor Server management events were constructing access contexts through
IHttpContextAccessor. The circuit context can lack the browser's current Device ID, so session validation returnsDeviceMismatchand denies otherwise valid Owner creation and Ladmin repair operations.Route these operations through the existing UltimateAuth browser JSON transport and protected Identity Lab endpoints. Validate the session/device once at the HTTP boundary, derive the actor from that context, and pass it into the existing application services. Provisioning rollback retargets the same validated flow to the created account while retaining actor checks, the trusted single-use rollback gate and the independent cleanup timeout.
The audit also migrates owner recovery and demo role/permission operations that had the same context dependency. Registration/availability remain anonymous workflows; existing browser SDK operations retain their transport.
apps/identity-lab/README.mddocuments the integration pattern and audit.Device ID enforcement, cookie settings, tenant isolation, ownership/capacity checks, Ladmin authorization, provisioning gates and UI repair confirmations remain enforced. Every new POST validates the existing UltimateAuth antiforgery token. Failures return safe messages and log server exceptions.
Validation (.NET SDK 10.0.403, net10.0):
UltimateAuthBuildTargetFrameworks=net10.0).git diff --checkpassed.The new regressions exercise session/device rejection, anonymous and revoked/invalid sessions, CSRF, server-derived actor identity, Owner/Member restrictions, foreign-sandbox targeting, capacity, role/membership creation, UI transport, and rollback identity/target/gate behavior. No planned checks remain blocked; no known remaining limitations in this scope.