-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Enabling admin page
IMPORTANT: It's heavily recommended to activate HTTPS before enabling this feature, to avoid possible MITM attacks.
This page allows a server administrator to view all the registered users and to delete them. It also allows inviting new users, even when registration is disabled.
To enable the admin page, you need to set an authentication token. This token can be anything, but it's recommended to use a long, randomly generated string of characters, for example running openssl rand -base64 48
. Keep this token secret, this is the password to access the admin area of your server!
To set the token, use the ADMIN_TOKEN
variable:
docker run -d --name bitwarden \
-e ADMIN_TOKEN=some_random_token_as_per_above_explanation \
-v /bw-data/:/data/ \
-p 80:80 \
bitwardenrs/server:latest
After this, the page will be available in the /admin
subdirectory.
The first time you save a setting in the admin page, config.json
will be generated in your DATA_FOLDER
. Values in this file will take precedence over the corresponding environment variable.
Note that config changes in the admin page do not take effect until you click the Save
button. For example, if you are testing SMTP settings, and you change the SMTP Auth mechanism
setting and then click Send test email
to test the change, this won't work as expected -- since you didn't click Save
, the SMTP Auth mechanism
change won't have taken effect.
Note: After changing the ADMIN_TOKEN
, the currently logged in admins will still be able to use their old login token for up to 20 minutes.
- Which container image to use
- Starting a container
- Updating the vaultwarden image
- Using Docker Compose
- Using Podman
- Building your own docker image
- Building binary
- Pre-built binaries
- Third-party packages
- Deployment examples
- Proxy examples
- Logrotate example
- Overview
- Disable registration of new users
- Disable invitations
- Enabling admin page
- Disable the admin token
- Enabling WebSocket notifications
- Enabling Mobile Client push notification
- Enabling U2F and FIDO2 WebAuthn authentication
- Enabling YubiKey OTP authentication
- Changing persistent data location
- Changing the API request size limit
- Changing the number of workers
- SMTP configuration
- Translating the email templates
- Password hint display
- Disabling or overriding the Vault interface hosting
- Logging
- Creating a systemd service
- Syncing users from LDAP
- Using an alternate base dir (subdir/subpath)
- Other configuration