Skip to content

Remember PKCE fallback clients across VS Code sessions - #634

Merged
clavery merged 2 commits into
mainfrom
fix/persist-pkce-fallback
Aug 22, 2026
Merged

Remember PKCE fallback clients across VS Code sessions#634
clavery merged 2 commits into
mainfrom
fix/persist-pkce-fallback

Conversation

@clavery

@clavery clavery commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • persist a PKCE-unsupported marker after a successful automatic implicit fallback, scoped by client ID and Account Manager host
  • reuse the compatible implicit session on later CLI processes and VS Code activations instead of repeating the known-failing PKCE browser flow
  • report that authorization was received in the PKCE callback instead of claiming authentication succeeded before token exchange
  • document the fallback behavior and migration override

Validation

  • pnpm --filter @salesforce/b2c-tooling-sdk run test:agent — 2,259 passing, 7 pending
  • pnpm run lint:agent
  • pnpm run typecheck:agent
  • SDK and VS Code builds
  • pnpm run docs:build
  • SDK formatting check

Fixes #633

@clavery
clavery deployed to b2c-docs-preview August 21, 2026 16:29 — with GitHub Actions Active
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

📘 Docs preview

🧹 The preview for this PR has been removed (PR closed).

@clavery
clavery merged commit 4dee938 into main Aug 22, 2026
11 checks passed
@clavery
clavery deleted the fix/persist-pkce-fallback branch August 22, 2026 00:23
@clavery
clavery deployed to b2c-docs-preview August 22, 2026 00:23 — with GitHub Actions Active
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.

Cursor / VSCode - Potential Double Authentication on Open (minor annoyance)

1 participant