[TrustedVault] Connection: support registration with unknown epoch
This CL adds support for authentication factor registration with unknown epoch/last key version. If that's the case, ListSecurityDomains request is sent first in order to detect the actual security domain epoch if it already exists and ensure that "last" trusted vault key is actually the last. Afterwards, JoinSecurityDomainsRequest is sent with detected epoch or with epoch=0 if security domain doesn't exist. In latter case, actual epoch will be detected using JoinSecurityDomainsResponse. Bug: 1113598 Change-Id: Ie7bc4104e0a909b9aece077c1b9eedbbcf1e8ae6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567157 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#842072}
Showing
Please register or sign in to comment