|
UnENVerse 0.42.6
Local-first desktop secrets manager — TypeScript frontend
|
import type;Functions | |
| function export | setRemoteFinishInitFn (fn:()=> Promise< void >) |
| Authenticate as a sub-user, asking for a second-factor code only if one is actually required. | |
| function | startPing () |
| function | stopPing () |
| function | genId () |
| function | saveSaved (list:RemoteVaultConfig[]) |
Variables | |
| let | _pingInterval |
| function export setRemoteFinishInitFn | ( | fn:(), | |
| Promise< void > | |||
| ) |
Authenticate as a sub-user, asking for a second-factor code only if one is actually required.
The server tells us the difference: a correct password on an account with a confirmed factor comes back 401 with totp_required, which the store raises as TotpRequiredError. Prompting up front instead would show a code box to every user, most of whom have no factor and nothing to type into it.
Shared by the Remote panel and the unlock screen so the two cannot drift — the unlock screen already carries a bug history of diverging from this path.
| function startPing | ( | ) |
| function stopPing | ( | ) |
| function genId | ( | ) |
| function saveSaved | ( | list:RemoteVaultConfig[] | ) |
| let _pingInterval |