Skip to content

feat(pin): invalidate persistent tokens on rejection and PIN change (4/5)#234

Draft
AlfioEmanueleFresta wants to merge 1 commit into
feat/pcmr-3-acquisitionfrom
feat/pcmr-4-invalidation
Draft

feat(pin): invalidate persistent tokens on rejection and PIN change (4/5)#234
AlfioEmanueleFresta wants to merge 1 commit into
feat/pcmr-3-acquisitionfrom
feat/pcmr-4-invalidation

Conversation

@AlfioEmanueleFresta
Copy link
Copy Markdown
Member

@AlfioEmanueleFresta AlfioEmanueleFresta commented May 30, 2026

Part 4 of 5 in a stack: #231, #232, #233, #234 (this), #235

This stack adds support for persistent pinUvAuthTokens (the CTAP 2.2+ pcmr permission), so a credential manager can list passkeys without re-prompting for the PIN on every launch or replug. Read-only credential management only.

This PR

Keeps stored tokens fresh:

  • If an authenticator rejects a stored token, it is evicted and a new one is minted transparently.
  • A local PIN change drops the stored token for that authenticator.
  • At mint time, a superseded token for the same device is cleaned up, while tokens belonging to other keys are left untouched.

@AlfioEmanueleFresta AlfioEmanueleFresta force-pushed the feat/pcmr-3-acquisition branch from 0fee3aa to b16de46 Compare May 30, 2026 17:24
@AlfioEmanueleFresta AlfioEmanueleFresta force-pushed the feat/pcmr-4-invalidation branch from bed6c79 to ada22af Compare May 30, 2026 17:24
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