A duplicated admin tab signs out its opener about an hour later
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- authentication, backend
Research direction
Read admin/src/FluentCMS.Admin/Authentication/AdminSession.cs:89-105 and the TwoTabsTests case that covers refreshes within the 30-second reuse leeway. Trace how session restore and refresh-token redemption interact across tabs, then add an end-to-end case for an opener and duplicate remaining signed in past an hour. Done means the test passes and a copied session drops its inherited refresh token before silently signing in through authorize.
Written by the indexing model from the issue text.
Description
Problem
A duplicated admin tab starts with the opener's sessionStorage and redeems the stored refresh token (admin/src/FluentCMS.Admin/Authentication/AdminSession.cs:89-105), while the opener still holds the same token in memory. At the opener's next refresh, well past the server's 30-second reuse leeway, it presents a redeemed token, gets invalid_grant and is sent to sign in. TwoTabsTests covers only refreshes within the leeway.
Proposal
Detect a copied session at restore (a per-tab id answered over BroadcastChannel); a copy drops the inherited refresh token and signs in silently through authorize.
Acceptance
- An opener and its duplicate both stay signed in past an hour
- An end-to-end case covers it
Found in the code review of 17 Nov 2026 (B9).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100