luzifer/vault-otp-ui
1
0
Fork 0
mirror of https://github.com/Luzifer/vault-otp-ui.git synced 2024-11-08 08:10:11 +00:00
Code Issues Releases Wiki Activity
Viewer for time based one-time passwords whose secret is stored in Vault
6 commits 5 branches 8 tags 3.9 MiB
Go 52.3%
HTML 23.2%
JavaScript 21.5%
Dockerfile 1.5%
Makefile 1.5%
Find a file
Knut Ahlers 9747d23de4
Add Dockerfile 
Signed-off-by: Knut Ahlers <knut@ahlers.me>
2017-06-14 22:08:45 +02:00
Godeps Vendor dependencies 2017-06-14 21:26:35 +02:00
vendor Vendor dependencies 2017-06-14 21:26:35 +02:00
.gitignore Initial version 2017-06-14 20:46:35 +02:00
.repo-runner.yaml Add CI building 2017-06-14 21:15:25 +02:00
application.coffee Initial version 2017-06-14 20:46:35 +02:00
application.js Initial version 2017-06-14 20:46:35 +02:00
assets.go Initial version 2017-06-14 20:46:35 +02:00
Dockerfile Add Dockerfile 2017-06-14 22:08:45 +02:00
index.html Initial version 2017-06-14 20:46:35 +02:00
LICENSE Add meta files 2017-06-14 22:07:21 +02:00
main.go Initial version 2017-06-14 20:46:35 +02:00
Makefile Add CI building 2017-06-14 21:15:25 +02:00
oauth.go Initial version 2017-06-14 20:46:35 +02:00
README.md Add meta files 2017-06-14 22:07:21 +02:00
token.go Stop using vault builtins 2017-06-14 21:26:35 +02:00

README.md

Luzifer / vault-otp-ui

vault-otp-ui is a viewer for time based one-time passwords whose secret is stored in Vault. After the Github oAuth2 login the interface features a clean list of tokens with their corresponding account names, a (regular expression capable) filter function, automatic refresh of the shown tokens after they got invalid and a mobile-friendly interface which allows the usage on any mobile phone.

Storage of the secrets

Two different methods are supported to store the secrets in Vault:

  • Vault 0.7.x included TOTP backend
  • Custom (generic) secrets containing secret, name, and icon keys

(When using the Vault builtin TOTP backend switching the icons for the tokens is not supported.)

Setup

  1. Create a new oAuth application
  2. Configure <your vault-otp-ui instance>/oauth2 as the callback URL
  3. Configure the Github authentication backend for your users to be able to read the keys containing the secrets / TOTP codes
  4. See vault-otp-ui --help for configuration parameters
    • You must configure the Github oAuth2 credentials
    • You must configure the Vault parameters
    • You should configure a session-secret having at least 64 byte length (If you don't set this it's chosen randomly which will invalidate your session cookies on every restart of the application)