Skip to content

feat(storage): carry chosen PCP kinds in authenticator transfers - #646

Closed
andreyudentsovottofeller wants to merge 2 commits into
dzejkop/pcp-storagefrom
andrej/pcp-transfer
Closed

andreyudentsovottofeller wants to merge 2 commits into
dzejkop/pcp-storagefrom
andrej/pcp-transfer

Conversation

@andreyudentsovottofeller

@andreyudentsovottofeller andreyudentsovottofeller commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Summary

WIP-109 hands the new authenticator a CredentialStore::export_vault_for_backup export, and deliberately keeps pcp_records out of backup exports. So after the vault migration a second device still receives the credential without its sealed package. For the NFC credential that is the document data itself: the backend cannot rebuild it, and the user is sent to re-scan.

WIP-109 sends the vault export to the new authenticator, but PCPs stay out of
backup exports, so a second device receives the credential and not the sealed
package it needs (an NFC document cannot be rebuilt by the backend).

Add export_vault_for_transfer(pcp_kinds), which appends the pcp_records of the
named kinds to the plaintext export so the host can stay under the WIP-109 size
limit, and merge_vault_from_transfer, which adds transferred credentials and any
PCP whose id is absent locally. Local PCPs are never replaced; backups keep
excluding PCPs; merge_vault_from_backup ignores the table, so the format id is
unchanged.
@andreyudentsovottofeller

Copy link
Copy Markdown
Contributor Author

Not relevant.

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