Skip to content

Fix stale MCP credentials and refresh expired-token 403 responses - #104

Merged
MathiasWP merged 1 commit into
mainfrom
fix-fiber-expired-token-cache
Sep 30, 2026
Merged

MathiasWP merged 1 commit into
mainfrom
fix-fiber-expired-token-cache

Conversation

@MathiasWP

Copy link
Copy Markdown
Owner

Fiber's MCP process could keep sending an expired browser token after the desktop app saved a replacement, especially when an API returned 403 Invalid token: jwt expired instead of 401.
Cached credentials now track saved keychain changes, credential-file contents, and authentication configuration; explicit 403 expiry errors trigger one refresh attempt while ordinary permission denials do not, and rejected retries are removed from the cache.
Includes updated MCP sign-in guidance, contributor documentation, a patch changeset, regression coverage, and credential-file test isolation that avoids process-wide environment changes.
Validation passed: 174 desktop tests, 145 headless tests, headless Clippy with warnings denied, and Rust formatting.

@MathiasWP
MathiasWP merged commit 4176f4f into main Sep 30, 2026
4 checks passed
@MathiasWP
MathiasWP deleted the fix-fiber-expired-token-cache branch September 30, 2026 13:21
@github-actions github-actions Bot mentioned this pull request Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant