CLI command

skarbiec totp verified

Record what the provider did with the last authenticator code a sign-in submitted, where the seed is kept, so the vault says whether the account accepts its seed, not only that the seed computes codes. Weles records every code it submits; the owner records a code he typed.

Invocation#

Shell
skarbiec totp verified (<item-id> | role:<role>) --outcome accepted|rejected|locked [--by owner|weles]

Purpose#

Record what the provider did with the last authenticator code a sign-in submitted, where the seed is kept, so the vault says whether the account accepts its seed, not only that the seed computes codes. Weles records every code it submits; the owner records a code he typed.

Required inputs and options#

  • The item or role:<role> keeping the seed, --outcome, and --by (owner when not given). POST /v1/operator/items/totp-verified takes id, outcome and by.

Output and state effects#

  • Writes context.verification {outcome, at, by} on the item keeping the seed (the identity a login signs in as, else the login), journals totp-verified and prints the item's verification: verified, rejected, locked, enrolled_pending (an enrolment added the authenticator and no code was submitted since; Google may keep asking for the phone for up to 7 days, support.google.com/accounts/answer/17137073), untested or none. totp seed, login identity list and doctor --check second-factor-seeds read the same record.

Refusals#

  • Every refusal is a declared cause of skarbiec.totp under /docs/errors. totp-verified-role-unheld: no live item plays the role. totp-verified-no-seed: the item keeps no seed, so no code could have been submitted. An --outcome or --by not among its values exits 2 naming them.