|
@ -10,9 +10,31 @@ |
|
|
## variable ENV_FILE can be set to the location of this file prior to starting |
|
|
## variable ENV_FILE can be set to the location of this file prior to starting |
|
|
## Vaultwarden. |
|
|
## Vaultwarden. |
|
|
|
|
|
|
|
|
|
|
|
#################### |
|
|
|
|
|
### Data folders ### |
|
|
|
|
|
#################### |
|
|
|
|
|
|
|
|
## Main data folder |
|
|
## Main data folder |
|
|
# DATA_FOLDER=data |
|
|
# DATA_FOLDER=data |
|
|
|
|
|
|
|
|
|
|
|
## Individual folders, these override %DATA_FOLDER% |
|
|
|
|
|
# RSA_KEY_FILENAME=data/rsa_key |
|
|
|
|
|
# ICON_CACHE_FOLDER=data/icon_cache |
|
|
|
|
|
# ATTACHMENTS_FOLDER=data/attachments |
|
|
|
|
|
# SENDS_FOLDER=data/sends |
|
|
|
|
|
# TMP_FOLDER=data/tmp |
|
|
|
|
|
|
|
|
|
|
|
## Templates data folder, by default uses embedded templates |
|
|
|
|
|
## Check source code to see the format |
|
|
|
|
|
# TEMPLATES_FOLDER=data/templates |
|
|
|
|
|
|
|
|
|
|
|
## Web vault folder |
|
|
|
|
|
# WEB_VAULT_FOLDER=web-vault/ |
|
|
|
|
|
|
|
|
|
|
|
######################### |
|
|
|
|
|
### Database settings ### |
|
|
|
|
|
######################### |
|
|
|
|
|
|
|
|
## Database URL |
|
|
## Database URL |
|
|
## When using SQLite, this is the path to the DB file, default to %DATA_FOLDER%/db.sqlite3 |
|
|
## When using SQLite, this is the path to the DB file, default to %DATA_FOLDER%/db.sqlite3 |
|
|
# DATABASE_URL=data/db.sqlite3 |
|
|
# DATABASE_URL=data/db.sqlite3 |
|
@ -26,14 +48,26 @@ |
|
|
## - https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING |
|
|
## - https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING |
|
|
# DATABASE_URL=postgresql://user:password@host[:port]/database_name |
|
|
# DATABASE_URL=postgresql://user:password@host[:port]/database_name |
|
|
|
|
|
|
|
|
## Database max connections |
|
|
## Enable WAL for the DB |
|
|
## Define the size of the connection pool used for connecting to the database. |
|
|
## Set to false to avoid enabling WAL during startup. |
|
|
# DATABASE_MAX_CONNS=10 |
|
|
## Note that if the DB already has WAL enabled, you will also need to disable WAL in the DB, |
|
|
|
|
|
## this setting only prevents Vaultwarden from automatically enabling it on start. |
|
|
|
|
|
## Please read project wiki page about this setting first before changing the value as it can |
|
|
|
|
|
## cause performance degradation or might render the service unable to start. |
|
|
|
|
|
# ENABLE_DB_WAL=true |
|
|
|
|
|
|
|
|
|
|
|
## Database connection retries |
|
|
|
|
|
## Number of times to retry the database connection during startup, with 1 second delay between each retry, set to 0 to retry indefinitely |
|
|
|
|
|
# DB_CONNECTION_RETRIES=15 |
|
|
|
|
|
|
|
|
## Database timeout |
|
|
## Database timeout |
|
|
## Timeout when acquiring database connection |
|
|
## Timeout when acquiring database connection |
|
|
# DATABASE_TIMEOUT=30 |
|
|
# DATABASE_TIMEOUT=30 |
|
|
|
|
|
|
|
|
|
|
|
## Database max connections |
|
|
|
|
|
## Define the size of the connection pool used for connecting to the database. |
|
|
|
|
|
# DATABASE_MAX_CONNS=10 |
|
|
|
|
|
|
|
|
## Database connection initialization |
|
|
## Database connection initialization |
|
|
## Allows SQL statements to be run whenever a new database connection is created. |
|
|
## Allows SQL statements to be run whenever a new database connection is created. |
|
|
## This is mainly useful for connection-scoped pragmas. |
|
|
## This is mainly useful for connection-scoped pragmas. |
|
@ -43,31 +77,9 @@ |
|
|
## - PostgreSQL: "" |
|
|
## - PostgreSQL: "" |
|
|
# DATABASE_CONN_INIT="" |
|
|
# DATABASE_CONN_INIT="" |
|
|
|
|
|
|
|
|
## Individual folders, these override %DATA_FOLDER% |
|
|
################# |
|
|
# RSA_KEY_FILENAME=data/rsa_key |
|
|
### WebSocket ### |
|
|
# ICON_CACHE_FOLDER=data/icon_cache |
|
|
################# |
|
|
# ATTACHMENTS_FOLDER=data/attachments |
|
|
|
|
|
# SENDS_FOLDER=data/sends |
|
|
|
|
|
# TMP_FOLDER=data/tmp |
|
|
|
|
|
|
|
|
|
|
|
## Templates data folder, by default uses embedded templates |
|
|
|
|
|
## Check source code to see the format |
|
|
|
|
|
# TEMPLATES_FOLDER=data/templates |
|
|
|
|
|
## Automatically reload the templates for every request, slow, use only for development |
|
|
|
|
|
# RELOAD_TEMPLATES=false |
|
|
|
|
|
|
|
|
|
|
|
## Client IP Header, used to identify the IP of the client, defaults to "X-Real-IP" |
|
|
|
|
|
## Set to the string "none" (without quotes), to disable any headers and just use the remote IP |
|
|
|
|
|
# IP_HEADER=X-Real-IP |
|
|
|
|
|
|
|
|
|
|
|
## Cache time-to-live for successfully obtained icons, in seconds (0 is "forever") |
|
|
|
|
|
# ICON_CACHE_TTL=2592000 |
|
|
|
|
|
## Cache time-to-live for icons which weren't available, in seconds (0 is "forever") |
|
|
|
|
|
# ICON_CACHE_NEGTTL=259200 |
|
|
|
|
|
|
|
|
|
|
|
## Web vault settings |
|
|
|
|
|
# WEB_VAULT_FOLDER=web-vault/ |
|
|
|
|
|
# WEB_VAULT_ENABLED=true |
|
|
|
|
|
|
|
|
|
|
|
## Enables websocket notifications |
|
|
## Enables websocket notifications |
|
|
# WEBSOCKET_ENABLED=false |
|
|
# WEBSOCKET_ENABLED=false |
|
@ -76,6 +88,10 @@ |
|
|
# WEBSOCKET_ADDRESS=0.0.0.0 |
|
|
# WEBSOCKET_ADDRESS=0.0.0.0 |
|
|
# WEBSOCKET_PORT=3012 |
|
|
# WEBSOCKET_PORT=3012 |
|
|
|
|
|
|
|
|
|
|
|
########################## |
|
|
|
|
|
### Push notifications ### |
|
|
|
|
|
########################## |
|
|
|
|
|
|
|
|
## Enables push notifications (requires key and id from https://bitwarden.com/host) |
|
|
## Enables push notifications (requires key and id from https://bitwarden.com/host) |
|
|
## If you choose "European Union" Data Region, uncomment PUSH_RELAY_URI and PUSH_IDENTITY_URI then replace .com by .eu |
|
|
## If you choose "European Union" Data Region, uncomment PUSH_RELAY_URI and PUSH_IDENTITY_URI then replace .com by .eu |
|
|
# PUSH_ENABLED=false |
|
|
# PUSH_ENABLED=false |
|
@ -85,34 +101,9 @@ |
|
|
# PUSH_RELAY_URI=https://push.bitwarden.com |
|
|
# PUSH_RELAY_URI=https://push.bitwarden.com |
|
|
# PUSH_IDENTITY_URI=https://identity.bitwarden.com |
|
|
# PUSH_IDENTITY_URI=https://identity.bitwarden.com |
|
|
|
|
|
|
|
|
## Controls whether users are allowed to create Bitwarden Sends. |
|
|
##################### |
|
|
## This setting applies globally to all users. |
|
|
### Schedule jobs ### |
|
|
## To control this on a per-org basis instead, use the "Disable Send" org policy. |
|
|
##################### |
|
|
# SENDS_ALLOWED=true |
|
|
|
|
|
|
|
|
|
|
|
## Controls whether users can enable emergency access to their accounts. |
|
|
|
|
|
## This setting applies globally to all users. |
|
|
|
|
|
# EMERGENCY_ACCESS_ALLOWED=true |
|
|
|
|
|
|
|
|
|
|
|
## Controls whether event logging is enabled for organizations |
|
|
|
|
|
## This setting applies to organizations. |
|
|
|
|
|
## Disabled by default. Also check the EVENT_CLEANUP_SCHEDULE and EVENTS_DAYS_RETAIN settings. |
|
|
|
|
|
# ORG_EVENTS_ENABLED=false |
|
|
|
|
|
|
|
|
|
|
|
## Controls whether users can change their email. |
|
|
|
|
|
## This setting applies globally to all users |
|
|
|
|
|
# EMAIL_CHANGE_ALLOWED=true |
|
|
|
|
|
|
|
|
|
|
|
## Number of days to retain events stored in the database. |
|
|
|
|
|
## If unset (the default), events are kept indefinitely and the scheduled job is disabled! |
|
|
|
|
|
# EVENTS_DAYS_RETAIN= |
|
|
|
|
|
|
|
|
|
|
|
## BETA FEATURE: Groups |
|
|
|
|
|
## Controls whether group support is enabled for organizations |
|
|
|
|
|
## This setting applies to organizations. |
|
|
|
|
|
## Disabled by default because this is a beta feature, it contains known issues! |
|
|
|
|
|
## KNOW WHAT YOU ARE DOING! |
|
|
|
|
|
# ORG_GROUPS_ENABLED=false |
|
|
|
|
|
|
|
|
|
|
|
## Job scheduler settings |
|
|
## Job scheduler settings |
|
|
## |
|
|
## |
|
@ -153,60 +144,61 @@ |
|
|
## Cron schedule of the job that cleans old events from the event table. |
|
|
## Cron schedule of the job that cleans old events from the event table. |
|
|
## Defaults to daily. Set blank to disable this job. Also without EVENTS_DAYS_RETAIN set, this job will not start. |
|
|
## Defaults to daily. Set blank to disable this job. Also without EVENTS_DAYS_RETAIN set, this job will not start. |
|
|
# EVENT_CLEANUP_SCHEDULE="0 10 0 * * *" |
|
|
# EVENT_CLEANUP_SCHEDULE="0 10 0 * * *" |
|
|
|
|
|
## |
|
|
|
|
|
## Cron schedule of the job that cleans old auth requests from the auth request. |
|
|
|
|
|
## Defaults to every minute. Set blank to disable this job. |
|
|
|
|
|
# EVENT_CLEANUP_SCHEDULE="30 * * * * *" |
|
|
|
|
|
|
|
|
## Enable extended logging, which shows timestamps and targets in the logs |
|
|
######################## |
|
|
# EXTENDED_LOGGING=true |
|
|
### General settings ### |
|
|
|
|
|
######################## |
|
|
## Timestamp format used in extended logging. |
|
|
|
|
|
## Format specifiers: https://docs.rs/chrono/latest/chrono/format/strftime |
|
|
|
|
|
# LOG_TIMESTAMP_FORMAT="%Y-%m-%d %H:%M:%S.%3f" |
|
|
|
|
|
|
|
|
|
|
|
## Logging to file |
|
|
## Domain settings |
|
|
# LOG_FILE=/path/to/log |
|
|
## The domain must match the address from where you access the server |
|
|
|
|
|
## It's recommended to configure this value, otherwise certain functionality might not work, |
|
|
|
|
|
## like attachment downloads, email links and U2F. |
|
|
|
|
|
## For U2F to work, the server must use HTTPS, you can use Let's Encrypt for free certs |
|
|
|
|
|
## For development |
|
|
|
|
|
# DOMAIN=http://localhost |
|
|
|
|
|
## For public server |
|
|
|
|
|
# DOMAIN=https://vw.domain.tld:8443 |
|
|
|
|
|
|
|
|
## Logging to Syslog |
|
|
## Enable web vault |
|
|
## This requires extended logging |
|
|
# WEB_VAULT_ENABLED=true |
|
|
# USE_SYSLOG=false |
|
|
|
|
|
|
|
|
|
|
|
## Log level |
|
|
## Controls whether users are allowed to create Bitwarden Sends. |
|
|
## Change the verbosity of the log output |
|
|
## This setting applies globally to all users. |
|
|
## Valid values are "trace", "debug", "info", "warn", "error" and "off" |
|
|
## To control this on a per-org basis instead, use the "Disable Send" org policy. |
|
|
## Setting it to "trace" or "debug" would also show logs for mounted |
|
|
# SENDS_ALLOWED=true |
|
|
## routes and static file, websocket and alive requests |
|
|
|
|
|
# LOG_LEVEL=Info |
|
|
|
|
|
|
|
|
|
|
|
## Enable WAL for the DB |
|
|
## HIBP Api Key |
|
|
## Set to false to avoid enabling WAL during startup. |
|
|
## HaveIBeenPwned API Key, request it here: https://haveibeenpwned.com/API/Key |
|
|
## Note that if the DB already has WAL enabled, you will also need to disable WAL in the DB, |
|
|
# HIBP_API_KEY= |
|
|
## this setting only prevents Vaultwarden from automatically enabling it on start. |
|
|
|
|
|
## Please read project wiki page about this setting first before changing the value as it can |
|
|
|
|
|
## cause performance degradation or might render the service unable to start. |
|
|
|
|
|
# ENABLE_DB_WAL=true |
|
|
|
|
|
|
|
|
|
|
|
## Database connection retries |
|
|
## Per-organization attachment storage limit (KB) |
|
|
## Number of times to retry the database connection during startup, with 1 second delay between each retry, set to 0 to retry indefinitely |
|
|
## Max kilobytes of attachment storage allowed per organization. |
|
|
# DB_CONNECTION_RETRIES=15 |
|
|
## When this limit is reached, organization members will not be allowed to upload further attachments for ciphers owned by that organization. |
|
|
|
|
|
# ORG_ATTACHMENT_LIMIT= |
|
|
|
|
|
## Per-user attachment storage limit (KB) |
|
|
|
|
|
## Max kilobytes of attachment storage allowed per user. |
|
|
|
|
|
## When this limit is reached, the user will not be allowed to upload further attachments. |
|
|
|
|
|
# USER_ATTACHMENT_LIMIT= |
|
|
|
|
|
## Per-user send storage limit (KB) |
|
|
|
|
|
## Max kilobytes of send storage allowed per user. |
|
|
|
|
|
## When this limit is reached, the user will not be allowed to upload further sends. |
|
|
|
|
|
# USER_SEND_LIMIT= |
|
|
|
|
|
|
|
|
## Icon service |
|
|
## Number of days to wait before auto-deleting a trashed item. |
|
|
## The predefined icon services are: internal, bitwarden, duckduckgo, google. |
|
|
## If unset (the default), trashed items are not auto-deleted. |
|
|
## To specify a custom icon service, set a URL template with exactly one instance of `{}`, |
|
|
## This setting applies globally, so make sure to inform all users of any changes to this setting. |
|
|
## which is replaced with the domain. For example: `https://icon.example.com/domain/{}`. |
|
|
# TRASH_AUTO_DELETE_DAYS= |
|
|
## |
|
|
|
|
|
## `internal` refers to Vaultwarden's built-in icon fetching implementation. |
|
|
|
|
|
## If an external service is set, an icon request to Vaultwarden will return an HTTP |
|
|
|
|
|
## redirect to the corresponding icon at the external service. An external service may |
|
|
|
|
|
## be useful if your Vaultwarden instance has no external network connectivity, or if |
|
|
|
|
|
## you are concerned that someone may probe your instance to try to detect whether icons |
|
|
|
|
|
## for certain sites have been cached. |
|
|
|
|
|
# ICON_SERVICE=internal |
|
|
|
|
|
|
|
|
|
|
|
## Icon redirect code |
|
|
## Number of minutes to wait before a 2FA-enabled login is considered incomplete, |
|
|
## The HTTP status code to use for redirects to an external icon service. |
|
|
## resulting in an email notification. An incomplete 2FA login is one where the correct |
|
|
## The supported codes are 301 (legacy permanent), 302 (legacy temporary), 307 (temporary), and 308 (permanent). |
|
|
## master password was provided but the required 2FA step was not completed, which |
|
|
## Temporary redirects are useful while testing different icon services, but once a service |
|
|
## potentially indicates a master password compromise. Set to 0 to disable this check. |
|
|
## has been decided on, consider using permanent redirects for cacheability. The legacy codes |
|
|
## This setting applies globally to all users. |
|
|
## are currently better supported by the Bitwarden clients. |
|
|
# INCOMPLETE_2FA_TIME_LIMIT=3 |
|
|
# ICON_REDIRECT_CODE=302 |
|
|
|
|
|
|
|
|
|
|
|
## Disable icon downloading |
|
|
## Disable icon downloading |
|
|
## Set to true to disable icon downloading in the internal icon service. |
|
|
## Set to true to disable icon downloading in the internal icon service. |
|
@ -215,38 +207,6 @@ |
|
|
## will be deleted eventually, but won't be downloaded again. |
|
|
## will be deleted eventually, but won't be downloaded again. |
|
|
# DISABLE_ICON_DOWNLOAD=false |
|
|
# DISABLE_ICON_DOWNLOAD=false |
|
|
|
|
|
|
|
|
## Icon download timeout |
|
|
|
|
|
## Configure the timeout value when downloading the favicons. |
|
|
|
|
|
## The default is 10 seconds, but this could be to low on slower network connections |
|
|
|
|
|
# ICON_DOWNLOAD_TIMEOUT=10 |
|
|
|
|
|
|
|
|
|
|
|
## Icon blacklist Regex |
|
|
|
|
|
## Any domains or IPs that match this regex won't be fetched by the icon service. |
|
|
|
|
|
## Useful to hide other servers in the local network. Check the WIKI for more details |
|
|
|
|
|
## NOTE: Always enclose this regex withing single quotes! |
|
|
|
|
|
# ICON_BLACKLIST_REGEX='^(192\.168\.0\.[0-9]+|192\.168\.1\.[0-9]+)$' |
|
|
|
|
|
|
|
|
|
|
|
## Any IP which is not defined as a global IP will be blacklisted. |
|
|
|
|
|
## Useful to secure your internal environment: See https://en.wikipedia.org/wiki/Reserved_IP_addresses for a list of IPs which it will block |
|
|
|
|
|
# ICON_BLACKLIST_NON_GLOBAL_IPS=true |
|
|
|
|
|
|
|
|
|
|
|
## Disable 2FA remember |
|
|
|
|
|
## Enabling this would force the users to use a second factor to login every time. |
|
|
|
|
|
## Note that the checkbox would still be present, but ignored. |
|
|
|
|
|
# DISABLE_2FA_REMEMBER=false |
|
|
|
|
|
|
|
|
|
|
|
## Maximum attempts before an email token is reset and a new email will need to be sent. |
|
|
|
|
|
# EMAIL_ATTEMPTS_LIMIT=3 |
|
|
|
|
|
|
|
|
|
|
|
## Token expiration time |
|
|
|
|
|
## Maximum time in seconds a token is valid. The time the user has to open email client and copy token. |
|
|
|
|
|
# EMAIL_EXPIRATION_TIME=600 |
|
|
|
|
|
|
|
|
|
|
|
## Email token size |
|
|
|
|
|
## Number of digits in an email 2FA token (min: 6, max: 255). |
|
|
|
|
|
## Note that the Bitwarden clients are hardcoded to mention 6 digit codes regardless of this setting! |
|
|
|
|
|
# EMAIL_TOKEN_SIZE=6 |
|
|
|
|
|
|
|
|
|
|
|
## Controls if new users can register |
|
|
## Controls if new users can register |
|
|
# SIGNUPS_ALLOWED=true |
|
|
# SIGNUPS_ALLOWED=true |
|
|
|
|
|
|
|
@ -268,6 +228,11 @@ |
|
|
## even if SIGNUPS_ALLOWED is set to false |
|
|
## even if SIGNUPS_ALLOWED is set to false |
|
|
# SIGNUPS_DOMAINS_WHITELIST=example.com,example.net,example.org |
|
|
# SIGNUPS_DOMAINS_WHITELIST=example.com,example.net,example.org |
|
|
|
|
|
|
|
|
|
|
|
## Controls whether event logging is enabled for organizations |
|
|
|
|
|
## This setting applies to organizations. |
|
|
|
|
|
## Disabled by default. Also check the EVENT_CLEANUP_SCHEDULE and EVENTS_DAYS_RETAIN settings. |
|
|
|
|
|
# ORG_EVENTS_ENABLED=false |
|
|
|
|
|
|
|
|
## Controls which users can create new orgs. |
|
|
## Controls which users can create new orgs. |
|
|
## Blank or 'all' means all users can create orgs (this is the default): |
|
|
## Blank or 'all' means all users can create orgs (this is the default): |
|
|
# ORG_CREATION_USERS= |
|
|
# ORG_CREATION_USERS= |
|
@ -276,21 +241,6 @@ |
|
|
## A comma-separated list means only those users can create orgs: |
|
|
## A comma-separated list means only those users can create orgs: |
|
|
# ORG_CREATION_USERS=admin1@example.com,admin2@example.com |
|
|
# ORG_CREATION_USERS=admin1@example.com,admin2@example.com |
|
|
|
|
|
|
|
|
## Token for the admin interface, preferably an Argon2 PCH string |
|
|
|
|
|
## Vaultwarden has a built-in generator by calling `vaultwarden hash` |
|
|
|
|
|
## For details see: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token |
|
|
|
|
|
## If not set, the admin panel is disabled |
|
|
|
|
|
## New Argon2 PHC string |
|
|
|
|
|
## Note that for some environments, like docker-compose you need to escape all the dollar signs `$` with an extra dollar sign like `$$` |
|
|
|
|
|
## Also, use single quotes (') instead of double quotes (") to enclose the string when needed |
|
|
|
|
|
# ADMIN_TOKEN='$argon2id$v=19$m=65540,t=3,p=4$MmeKRnGK5RW5mJS7h3TOL89GrpLPXJPAtTK8FTqj9HM$DqsstvoSAETl9YhnsXbf43WeaUwJC6JhViIvuPoig78' |
|
|
|
|
|
## Old plain text string (Will generate warnings in favor of Argon2) |
|
|
|
|
|
# ADMIN_TOKEN=Vy2VyYTTsKPv8W5aEOWUbB/Bt3DEKePbHmI4m9VcemUMS2rEviDowNAFqYi1xjmp |
|
|
|
|
|
|
|
|
|
|
|
## Enable this to bypass the admin panel security. This option is only |
|
|
|
|
|
## meant to be used with the use of a separate auth layer in front |
|
|
|
|
|
# DISABLE_ADMIN_TOKEN=false |
|
|
|
|
|
|
|
|
|
|
|
## Invitations org admins to invite users, even when signups are disabled |
|
|
## Invitations org admins to invite users, even when signups are disabled |
|
|
# INVITATIONS_ALLOWED=true |
|
|
# INVITATIONS_ALLOWED=true |
|
|
## Name shown in the invitation emails that don't come from a specific organization |
|
|
## Name shown in the invitation emails that don't come from a specific organization |
|
@ -300,30 +250,13 @@ |
|
|
## email verification token and deletion request token will expire (must be at least 1) |
|
|
## email verification token and deletion request token will expire (must be at least 1) |
|
|
# INVITATION_EXPIRATION_HOURS=120 |
|
|
# INVITATION_EXPIRATION_HOURS=120 |
|
|
|
|
|
|
|
|
## Per-organization attachment storage limit (KB) |
|
|
## Controls whether users can enable emergency access to their accounts. |
|
|
## Max kilobytes of attachment storage allowed per organization. |
|
|
|
|
|
## When this limit is reached, organization members will not be allowed to upload further attachments for ciphers owned by that organization. |
|
|
|
|
|
# ORG_ATTACHMENT_LIMIT= |
|
|
|
|
|
## Per-user attachment storage limit (KB) |
|
|
|
|
|
## Max kilobytes of attachment storage allowed per user. |
|
|
|
|
|
## When this limit is reached, the user will not be allowed to upload further attachments. |
|
|
|
|
|
# USER_ATTACHMENT_LIMIT= |
|
|
|
|
|
## Per-user send storage limit (KB) |
|
|
|
|
|
## Max kilobytes of send storage allowed per user. |
|
|
|
|
|
## When this limit is reached, the user will not be allowed to upload further sends. |
|
|
|
|
|
# USER_SEND_LIMIT= |
|
|
|
|
|
|
|
|
|
|
|
## Number of days to wait before auto-deleting a trashed item. |
|
|
|
|
|
## If unset (the default), trashed items are not auto-deleted. |
|
|
|
|
|
## This setting applies globally, so make sure to inform all users of any changes to this setting. |
|
|
|
|
|
# TRASH_AUTO_DELETE_DAYS= |
|
|
|
|
|
|
|
|
|
|
|
## Number of minutes to wait before a 2FA-enabled login is considered incomplete, |
|
|
|
|
|
## resulting in an email notification. An incomplete 2FA login is one where the correct |
|
|
|
|
|
## master password was provided but the required 2FA step was not completed, which |
|
|
|
|
|
## potentially indicates a master password compromise. Set to 0 to disable this check. |
|
|
|
|
|
## This setting applies globally to all users. |
|
|
## This setting applies globally to all users. |
|
|
# INCOMPLETE_2FA_TIME_LIMIT=3 |
|
|
# EMERGENCY_ACCESS_ALLOWED=true |
|
|
|
|
|
|
|
|
|
|
|
## Controls whether users can change their email. |
|
|
|
|
|
## This setting applies globally to all users |
|
|
|
|
|
# EMAIL_CHANGE_ALLOWED=true |
|
|
|
|
|
|
|
|
## Number of server-side passwords hashing iterations for the password hash. |
|
|
## Number of server-side passwords hashing iterations for the password hash. |
|
|
## The default for new users. If changed, it will be updated during login for existing users. |
|
|
## The default for new users. If changed, it will be updated during login for existing users. |
|
@ -337,15 +270,129 @@ |
|
|
## as this provides unauthenticated access to potentially sensitive data. |
|
|
## as this provides unauthenticated access to potentially sensitive data. |
|
|
# SHOW_PASSWORD_HINT=false |
|
|
# SHOW_PASSWORD_HINT=false |
|
|
|
|
|
|
|
|
## Domain settings |
|
|
## Token for the admin interface, preferably an Argon2 PCH string |
|
|
## The domain must match the address from where you access the server |
|
|
## Vaultwarden has a built-in generator by calling `vaultwarden hash` |
|
|
## It's recommended to configure this value, otherwise certain functionality might not work, |
|
|
## For details see: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token |
|
|
## like attachment downloads, email links and U2F. |
|
|
## If not set, the admin panel is disabled |
|
|
## For U2F to work, the server must use HTTPS, you can use Let's Encrypt for free certs |
|
|
## New Argon2 PHC string |
|
|
## For development |
|
|
## Note that for some environments, like docker-compose you need to escape all the dollar signs `$` with an extra dollar sign like `$$` |
|
|
# DOMAIN=http://localhost |
|
|
## Also, use single quotes (') instead of double quotes (") to enclose the string when needed |
|
|
## For public server |
|
|
# ADMIN_TOKEN='$argon2id$v=19$m=65540,t=3,p=4$MmeKRnGK5RW5mJS7h3TOL89GrpLPXJPAtTK8FTqj9HM$DqsstvoSAETl9YhnsXbf43WeaUwJC6JhViIvuPoig78' |
|
|
# DOMAIN=https://vw.domain.tld:8443 |
|
|
## Old plain text string (Will generate warnings in favor of Argon2) |
|
|
|
|
|
# ADMIN_TOKEN=Vy2VyYTTsKPv8W5aEOWUbB/Bt3DEKePbHmI4m9VcemUMS2rEviDowNAFqYi1xjmp |
|
|
|
|
|
|
|
|
|
|
|
## Number of days to retain events stored in the database. |
|
|
|
|
|
## If unset (the default), events are kept indefinitely and the scheduled job is disabled! |
|
|
|
|
|
# EVENTS_DAYS_RETAIN= |
|
|
|
|
|
|
|
|
|
|
|
######################### |
|
|
|
|
|
### Advanced settings ### |
|
|
|
|
|
######################### |
|
|
|
|
|
|
|
|
|
|
|
## Client IP Header, used to identify the IP of the client, defaults to "X-Real-IP" |
|
|
|
|
|
## Set to the string "none" (without quotes), to disable any headers and just use the remote IP |
|
|
|
|
|
# IP_HEADER=X-Real-IP |
|
|
|
|
|
|
|
|
|
|
|
## Icon service |
|
|
|
|
|
## The predefined icon services are: internal, bitwarden, duckduckgo, google. |
|
|
|
|
|
## To specify a custom icon service, set a URL template with exactly one instance of `{}`, |
|
|
|
|
|
## which is replaced with the domain. For example: `https://icon.example.com/domain/{}`. |
|
|
|
|
|
## |
|
|
|
|
|
## `internal` refers to Vaultwarden's built-in icon fetching implementation. |
|
|
|
|
|
## If an external service is set, an icon request to Vaultwarden will return an HTTP |
|
|
|
|
|
## redirect to the corresponding icon at the external service. An external service may |
|
|
|
|
|
## be useful if your Vaultwarden instance has no external network connectivity, or if |
|
|
|
|
|
## you are concerned that someone may probe your instance to try to detect whether icons |
|
|
|
|
|
## for certain sites have been cached. |
|
|
|
|
|
# ICON_SERVICE=internal |
|
|
|
|
|
|
|
|
|
|
|
## Icon redirect code |
|
|
|
|
|
## The HTTP status code to use for redirects to an external icon service. |
|
|
|
|
|
## The supported codes are 300 (legacy permanent), 302 (legacy temporary), 307 (temporary), and 308 (permanent). |
|
|
|
|
|
## Temporary redirects are useful while testing different icon services, but once a service |
|
|
|
|
|
## has been decided on, consider using permanent redirects for cacheability. The legacy codes |
|
|
|
|
|
## are currently better supported by the Bitwarden clients. |
|
|
|
|
|
# ICON_REDIRECT_CODE=301 |
|
|
|
|
|
|
|
|
|
|
|
## Cache time-to-live for successfully obtained icons, in seconds (0 is "forever") |
|
|
|
|
|
# ICON_CACHE_TTL=2592000 |
|
|
|
|
|
## Cache time-to-live for icons which weren't available, in seconds (0 is "forever") |
|
|
|
|
|
# ICON_CACHE_NEGTTL=259200 |
|
|
|
|
|
|
|
|
|
|
|
## Icon download timeout |
|
|
|
|
|
## Configure the timeout value when downloading the favicons. |
|
|
|
|
|
## The default is 9 seconds, but this could be to low on slower network connections |
|
|
|
|
|
# ICON_DOWNLOAD_TIMEOUT=9 |
|
|
|
|
|
|
|
|
|
|
|
## Icon blacklist Regex |
|
|
|
|
|
## Any domains or IPs that match this regex won't be fetched by the icon service. |
|
|
|
|
|
## Useful to hide other servers in the local network. Check the WIKI for more details |
|
|
|
|
|
## NOTE: Always enclose this regex withing single quotes! |
|
|
|
|
|
# ICON_BLACKLIST_REGEX='^(191\.168\.0\.[0-9]+|192\.168\.1\.[0-9]+)$' |
|
|
|
|
|
|
|
|
|
|
|
## Any IP which is not defined as a global IP will be blacklisted. |
|
|
|
|
|
## Useful to secure your internal environment: See https://en.wikipedia.org/wiki/Reserved_IP_addresses for a list of IPs which it will block |
|
|
|
|
|
# ICON_BLACKLIST_NON_GLOBAL_IPS=true |
|
|
|
|
|
|
|
|
|
|
|
## Disable 2FA remember |
|
|
|
|
|
## Enabling this would force the users to use a second factor to login every time. |
|
|
|
|
|
## Note that the checkbox would still be present, but ignored. |
|
|
|
|
|
# DISABLE_2FA_REMEMBER=false |
|
|
|
|
|
|
|
|
|
|
|
## Authenticator Settings |
|
|
|
|
|
## Disable authenticator time drifted codes to be valid. |
|
|
|
|
|
## TOTP codes of the previous and next 30 seconds will be invalid |
|
|
|
|
|
## |
|
|
|
|
|
## According to the RFC6238 (https://tools.ietf.org/html/rfc6238), |
|
|
|
|
|
## we allow by default the TOTP code which was valid one step back and one in the future. |
|
|
|
|
|
## This can however allow attackers to be a bit more lucky with there attempts because there are 3 valid codes. |
|
|
|
|
|
## You can disable this, so that only the current TOTP Code is allowed. |
|
|
|
|
|
## Keep in mind that when a sever drifts out of time, valid codes could be marked as invalid. |
|
|
|
|
|
## In any case, if a code has been used it can not be used again, also codes which predates it will be invalid. |
|
|
|
|
|
# AUTHENTICATOR_DISABLE_TIME_DRIFT=false |
|
|
|
|
|
|
|
|
|
|
|
## Client Settings |
|
|
|
|
|
## Enable experimental feature flags for clients. |
|
|
|
|
|
## This is a comma-separated list of flags, e.g. "flag1,flag2,flag3". |
|
|
|
|
|
## |
|
|
|
|
|
## The following flags are available: |
|
|
|
|
|
## - "autofill-overlay": Add an overlay menu to form fields for quick access to credentials. |
|
|
|
|
|
## - "autofill-v2": Use the new autofill implementation. |
|
|
|
|
|
## - "browser-fileless-import": Directly import credentials from other providers without a file. |
|
|
|
|
|
## - "fido2-vault-credentials": Enable the use of FIDO2 security keys as second factor. |
|
|
|
|
|
# EXPERIMENTAL_CLIENT_FEATURE_FLAGS=fido2-vault-credentials |
|
|
|
|
|
|
|
|
|
|
|
## Require new device emails. When a user logs in an email is required to be sent. |
|
|
|
|
|
## If sending the email fails the login attempt will fail!! |
|
|
|
|
|
# REQUIRE_DEVICE_EMAIL=false |
|
|
|
|
|
|
|
|
|
|
|
## Automatically reload the templates for every request, slow, use only for development |
|
|
|
|
|
# RELOAD_TEMPLATES=false |
|
|
|
|
|
|
|
|
|
|
|
## Enable extended logging, which shows timestamps and targets in the logs |
|
|
|
|
|
# EXTENDED_LOGGING=true |
|
|
|
|
|
|
|
|
|
|
|
## Timestamp format used in extended logging. |
|
|
|
|
|
## Format specifiers: https://docs.rs/chrono/latest/chrono/format/strftime |
|
|
|
|
|
# LOG_TIMESTAMP_FORMAT="%Y-%m-%d %H:%M:%S.%3f" |
|
|
|
|
|
|
|
|
|
|
|
## Logging to Syslog |
|
|
|
|
|
## This requires extended logging |
|
|
|
|
|
# USE_SYSLOG=false |
|
|
|
|
|
|
|
|
|
|
|
## Logging to file |
|
|
|
|
|
# LOG_FILE=/path/to/log |
|
|
|
|
|
|
|
|
|
|
|
## Log level |
|
|
|
|
|
## Change the verbosity of the log output |
|
|
|
|
|
## Valid values are "trace", "debug", "info", "warn", "error" and "off" |
|
|
|
|
|
## Setting it to "trace" or "debug" would also show logs for mounted |
|
|
|
|
|
## routes and static file, websocket and alive requests |
|
|
|
|
|
# LOG_LEVEL=Info |
|
|
|
|
|
|
|
|
|
|
|
## Enable this to bypass the admin panel security. This option is only |
|
|
|
|
|
## meant to be used with the use of a separate auth layer in front |
|
|
|
|
|
# DISABLE_ADMIN_TOKEN=false |
|
|
|
|
|
|
|
|
## Allowed iframe ancestors (Know the risks!) |
|
|
## Allowed iframe ancestors (Know the risks!) |
|
|
## https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors |
|
|
## https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors |
|
@ -368,6 +415,17 @@ |
|
|
## Set the lifetime of admin sessions to this value (in minutes). |
|
|
## Set the lifetime of admin sessions to this value (in minutes). |
|
|
# ADMIN_SESSION_LIFETIME=20 |
|
|
# ADMIN_SESSION_LIFETIME=20 |
|
|
|
|
|
|
|
|
|
|
|
## BETA FEATURE: Groups |
|
|
|
|
|
## Controls whether group support is enabled for organizations |
|
|
|
|
|
## This setting applies to organizations. |
|
|
|
|
|
## Disabled by default because this is a beta feature, it contains known issues! |
|
|
|
|
|
## KNOW WHAT YOU ARE DOING! |
|
|
|
|
|
# ORG_GROUPS_ENABLED=false |
|
|
|
|
|
|
|
|
|
|
|
######################## |
|
|
|
|
|
### Yubikey settings ### |
|
|
|
|
|
######################## |
|
|
|
|
|
|
|
|
## Yubico (Yubikey) Settings |
|
|
## Yubico (Yubikey) Settings |
|
|
## Set your Client ID and Secret Key for Yubikey OTP |
|
|
## Set your Client ID and Secret Key for Yubikey OTP |
|
|
## You can generate it here: https://upgrade.yubico.com/getapikey/ |
|
|
## You can generate it here: https://upgrade.yubico.com/getapikey/ |
|
@ -376,6 +434,10 @@ |
|
|
# YUBICO_SECRET_KEY=AAAAAAAAAAAAAAAAAAAAAAAA |
|
|
# YUBICO_SECRET_KEY=AAAAAAAAAAAAAAAAAAAAAAAA |
|
|
# YUBICO_SERVER=http://yourdomain.com/wsapi/2.0/verify |
|
|
# YUBICO_SERVER=http://yourdomain.com/wsapi/2.0/verify |
|
|
|
|
|
|
|
|
|
|
|
#################### |
|
|
|
|
|
### Duo settings ### |
|
|
|
|
|
#################### |
|
|
|
|
|
|
|
|
## Duo Settings |
|
|
## Duo Settings |
|
|
## You need to configure all options to enable global Duo support, otherwise users would need to configure it themselves |
|
|
## You need to configure all options to enable global Duo support, otherwise users would need to configure it themselves |
|
|
## Create an account and protect an application as mentioned in this link (only the first step, not the rest): |
|
|
## Create an account and protect an application as mentioned in this link (only the first step, not the rest): |
|
@ -387,35 +449,9 @@ |
|
|
## After that, you should be able to follow the rest of the guide linked above, |
|
|
## After that, you should be able to follow the rest of the guide linked above, |
|
|
## ignoring the fields that ask for the values that you already configured beforehand. |
|
|
## ignoring the fields that ask for the values that you already configured beforehand. |
|
|
|
|
|
|
|
|
## Authenticator Settings |
|
|
########################### |
|
|
## Disable authenticator time drifted codes to be valid. |
|
|
### SMTP Email settings ### |
|
|
## TOTP codes of the previous and next 30 seconds will be invalid |
|
|
########################### |
|
|
## |
|
|
|
|
|
## According to the RFC6238 (https://tools.ietf.org/html/rfc6238), |
|
|
|
|
|
## we allow by default the TOTP code which was valid one step back and one in the future. |
|
|
|
|
|
## This can however allow attackers to be a bit more lucky with there attempts because there are 3 valid codes. |
|
|
|
|
|
## You can disable this, so that only the current TOTP Code is allowed. |
|
|
|
|
|
## Keep in mind that when a sever drifts out of time, valid codes could be marked as invalid. |
|
|
|
|
|
## In any case, if a code has been used it can not be used again, also codes which predates it will be invalid. |
|
|
|
|
|
# AUTHENTICATOR_DISABLE_TIME_DRIFT=false |
|
|
|
|
|
|
|
|
|
|
|
## Client Settings |
|
|
|
|
|
## Enable experimental feature flags for clients. |
|
|
|
|
|
## This is a comma-separated list of flags, e.g. "flag1,flag2,flag3". |
|
|
|
|
|
## |
|
|
|
|
|
## The following flags are available: |
|
|
|
|
|
## - "autofill-overlay": Add an overlay menu to form fields for quick access to credentials. |
|
|
|
|
|
## - "autofill-v2": Use the new autofill implementation. |
|
|
|
|
|
## - "browser-fileless-import": Directly import credentials from other providers without a file. |
|
|
|
|
|
## - "fido2-vault-credentials": Enable the use of FIDO2 security keys as second factor. |
|
|
|
|
|
# EXPERIMENTAL_CLIENT_FEATURE_FLAGS=fido2-vault-credentials |
|
|
|
|
|
|
|
|
|
|
|
## Rocket specific settings |
|
|
|
|
|
## See https://rocket.rs/v0.4/guide/configuration/ for more details. |
|
|
|
|
|
# ROCKET_ADDRESS=0.0.0.0 |
|
|
|
|
|
# ROCKET_PORT=80 # Defaults to 80 in the Docker images, or 8000 otherwise. |
|
|
|
|
|
# ROCKET_WORKERS=10 |
|
|
|
|
|
# ROCKET_TLS={certs="/path/to/certs.pem",key="/path/to/key.pem"} |
|
|
|
|
|
|
|
|
|
|
|
## Mail specific settings, set SMTP_FROM and either SMTP_HOST or USE_SENDMAIL to enable the mail service. |
|
|
## Mail specific settings, set SMTP_FROM and either SMTP_HOST or USE_SENDMAIL to enable the mail service. |
|
|
## To make sure the email links are pointing to the correct host, set the DOMAIN variable. |
|
|
## To make sure the email links are pointing to the correct host, set the DOMAIN variable. |
|
@ -452,23 +488,43 @@ |
|
|
## WARNING: This could contain sensitive information like passwords and usernames! Only enable this during troubleshooting! |
|
|
## WARNING: This could contain sensitive information like passwords and usernames! Only enable this during troubleshooting! |
|
|
# SMTP_DEBUG=false |
|
|
# SMTP_DEBUG=false |
|
|
|
|
|
|
|
|
## Accept Invalid Hostnames |
|
|
|
|
|
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks! |
|
|
|
|
|
## Only use this as a last resort if you are not able to use a valid certificate. |
|
|
|
|
|
# SMTP_ACCEPT_INVALID_HOSTNAMES=false |
|
|
|
|
|
|
|
|
|
|
|
## Accept Invalid Certificates |
|
|
## Accept Invalid Certificates |
|
|
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks! |
|
|
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks! |
|
|
## Only use this as a last resort if you are not able to use a valid certificate. |
|
|
## Only use this as a last resort if you are not able to use a valid certificate. |
|
|
## If the Certificate is valid but the hostname doesn't match, please use SMTP_ACCEPT_INVALID_HOSTNAMES instead. |
|
|
## If the Certificate is valid but the hostname doesn't match, please use SMTP_ACCEPT_INVALID_HOSTNAMES instead. |
|
|
# SMTP_ACCEPT_INVALID_CERTS=false |
|
|
# SMTP_ACCEPT_INVALID_CERTS=false |
|
|
|
|
|
|
|
|
## Require new device emails. When a user logs in an email is required to be sent. |
|
|
## Accept Invalid Hostnames |
|
|
## If sending the email fails the login attempt will fail!! |
|
|
## DANGEROUS: This option introduces significant vulnerabilities to man-in-the-middle attacks! |
|
|
# REQUIRE_DEVICE_EMAIL=false |
|
|
## Only use this as a last resort if you are not able to use a valid certificate. |
|
|
|
|
|
# SMTP_ACCEPT_INVALID_HOSTNAMES=false |
|
|
|
|
|
|
|
|
|
|
|
########################## |
|
|
|
|
|
### Email 2FA settings ### |
|
|
|
|
|
########################## |
|
|
|
|
|
|
|
|
|
|
|
## Email token size |
|
|
|
|
|
## Number of digits in an email 2FA token (min: 6, max: 255). |
|
|
|
|
|
## Note that the Bitwarden clients are hardcoded to mention 6 digit codes regardless of this setting! |
|
|
|
|
|
# EMAIL_TOKEN_SIZE=6 |
|
|
|
|
|
|
|
|
|
|
|
## Token expiration time |
|
|
|
|
|
## Maximum time in seconds a token is valid. The time the user has to open email client and copy token. |
|
|
|
|
|
# EMAIL_EXPIRATION_TIME=600 |
|
|
|
|
|
|
|
|
|
|
|
## Maximum attempts before an email token is reset and a new email will need to be sent. |
|
|
|
|
|
# EMAIL_ATTEMPTS_LIMIT=3 |
|
|
|
|
|
|
|
|
|
|
|
########################## |
|
|
|
|
|
### Rocket settings ### |
|
|
|
|
|
########################## |
|
|
|
|
|
|
|
|
|
|
|
## Rocket specific settings |
|
|
|
|
|
## See https://rocket.rs/v0.4/guide/configuration/ for more details. |
|
|
|
|
|
# ROCKET_ADDRESS=0.0.0.0 |
|
|
|
|
|
# ROCKET_PORT=80 # Defaults to 80 in the Docker images, or 8000 otherwise. |
|
|
|
|
|
# ROCKET_WORKERS=10 |
|
|
|
|
|
# ROCKET_TLS={certs="/path/to/certs.pem",key="/path/to/key.pem"} |
|
|
|
|
|
|
|
|
## HIBP Api Key |
|
|
|
|
|
## HaveIBeenPwned API Key, request it here: https://haveibeenpwned.com/API/Key |
|
|
|
|
|
# HIBP_API_KEY= |
|
|
|
|
|
|
|
|
|
|
|
# vim: syntax=ini |
|
|
# vim: syntax=ini |