From f0327bae95213cbec8df768139d8088f2cab8184 Mon Sep 17 00:00:00 2001 From: Knut Ahlers Date: Sat, 14 Sep 2019 15:44:54 +0200 Subject: [PATCH] Update docs for new possibilities Signed-off-by: Knut Ahlers --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 6e0a69d..a232876 100644 --- a/README.md +++ b/README.md @@ -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.)