-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Enabling Yubikey OTP authentication
Proxymiity ☆ edited this page Apr 29, 2021
·
6 revisions
To enable YubiKey authentication, you must set the YUBICO_CLIENT_ID
and YUBICO_SECRET_KEY
env variables.
If YUBICO_SERVER
is not specified, it will use the default YubiCloud servers. You can generate YUBICO_CLIENT_ID
and YUBICO_SECRET_KEY
for the default YubiCloud here.
Notes:
- In order to generate API keys or use a YubiKey with an OTP server, it must be registered. After configuring your key in the YubiKey Personalization Tool, you can register it with the default servers here.
- aarch64 builds of the server version 1.6.0 or older do not support Yubikey functionality due to upstream issues - see #262.
docker run -d --name bitwarden \
-e YUBICO_CLIENT_ID=12345 \
-e YUBICO_SECRET_KEY=ABCDEABCDEABCDEABCDE= \
-v /vw-data/:/data/ \
-p 80:80 \
vaultwarden/server:latest
- Which container image to use
- Starting a container
- Using Docker Compose
- Using Podman
- Updating the vaultwarden image
- Overview
- Enabling admin page
- SMTP configuration
- Disable registration of new users
- Disable invitations
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Other configuration
- Using the MariaDB (MySQL) Backend
- Using the PostgreSQL Backend
- Running without WAL enabled
- Migrating from MariaDB (MySQL) to SQLite
- Hardening Guide
- Password hint display
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Fail2Ban Setup
- Fail2Ban + ModSecurity + Traefik + Docker
- Translating the email templates
- Translating admin page
- Customize Vaultwarden CSS
- Disabling or overriding the Vault interface hosting
- Building binary
- Building your own docker image
- Git hooks
- Differences from the upstream API implementation