Repository navigation
Fix fresh-cookie actor restoration in Web Console 1.6.197 - #228
Merged
Merged
Conversation
chen21019
marked this pull request as ready for review
October 29, 2026 11:30
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.
Valid cookies opened in a fresh browser context could restore a session with a null actor, preventing the human approval inbox from loading. This change resolves a missing actor from the authenticated API root's
X-Api-User-Idafter validating the current-token identity, then repairs only the matching legacy session under the existing mutex.The token endpoint's virtual-account headers are ignored. Cookie changes, newer generations, conflicting actors, unauthenticated login options and permission failures retain their fail-closed handling. Added focused cases cover these boundaries and two-tab recovery. The component version is 1.6.197; the seven-tool shared engine and standalone bridge 0.1.0 are unchanged.
Validation: 31 targeted local session tests passed. Full producer 40866485520 passed all 1,121 Ember tests, existing security/static checks, reproducible double build and SBOM generation with an enabled build ceiling and initial mode off. CodeQL passed both analyses and reported no new alerts. Independent backend review found no blocking issue. Server555 deployment acceptance remains separate.