mirror of
https://github.com/Luzifer/vault-otp-ui.git
synced 2024-11-08 08:10:11 +00:00
Update docs for new possibilities
Signed-off-by: Knut Ahlers <knut@ahlers.me>
This commit is contained in:
parent
0937514785
commit
f0327bae95
1 changed files with 3 additions and 2 deletions
|
@ -13,10 +13,11 @@
|
|||
Two different methods are supported to store the secrets in Vault:
|
||||
|
||||
- Vault 0.7.x included [TOTP backend](https://www.vaultproject.io/docs/secrets/totp/index.html)
|
||||
- Custom (generic) secrets containing `secret`, `name`, `digits`, and `icon` keys
|
||||
- Custom (generic) secrets containing `secret`, `name`, `digits`, `period`, and `icon` keys
|
||||
- Icons supported are to be chosen from [FontAwesome](http://fontawesome.io/) icon set
|
||||
- When no `name` is set the Vault key will be used as a name
|
||||
- The `digits` field supports the values `6` (default) and `8` to generate longer 8-digit-codes
|
||||
- The `digits` field supports the values `6` (default), `7` for Authy-imported codes and `8` to generate longer 8-digit-codes (basically it supports any number but those are the real-life examples I've seen until now)
|
||||
- The `period` field by default uses `30` seconds but can be set to any other number (like `10` for Authy-imported codes)
|
||||
|
||||
(When using the Vault builtin TOTP backend switching the icons for the tokens is not supported.)
|
||||
|
||||
|
|
Loading…
Reference in a new issue