[GH-ISSUE #849] Allow empty ADMIN_TOKEN when DISABLE_ADMIN_TOKEN is set to false #600

New issue

Closed

opened 2026-03-03 02:01:11 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:01:11 +03:00

Owner

Originally created by @Roxedus on GitHub (Feb 5, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/849

Allow presenting the variable for the user(which in reality set it to NULL), but disabling the admin panel when DISABLE_ADMIN_TOKEN is explicit set to false

As you may be aware of trough #813, I control this template, and would like to present the user with the ability to use ADMIN_TOKEN, in order to this I have to set it to NULL.

The reason that I want to present it this way is because it is a easier way to set settings in favor of environment variables. This is only also the only way to get started without enabling signup afaik.

Expected behaviour

Using the environment variables -e ADMIN_TOKEN="" AND -e DISABLE_ADMIN_TOKEN=false should not enable the admin panel, but still allow the container to run, due to explicit telling bitwarden to disallow insecure token, while the admin_token variable exists.

Actual behaviour

Using the environment variables -e ADMIN_TOKEN="" AND -e DISABLE_ADMIN_TOKEN=false gives me the error about either removing/filling the admin_token

Originally created by @Roxedus on GitHub (Feb 5, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/849 ### Allow presenting the variable for the user(which in reality set it to NULL), but disabling the admin panel when DISABLE_ADMIN_TOKEN is explicit set to false As you may be aware of trough #813, I control this template, and would like to present the user with the ability to use `ADMIN_TOKEN`, in order to this I have to set it to NULL. The reason that I want to present it this way is because it is a easier way to set settings in favor of environment variables. This is only also the only way to get started without enabling signup afaik. ### Expected behaviour Using the environment variables `-e ADMIN_TOKEN=""` AND `-e DISABLE_ADMIN_TOKEN=false` should not enable the admin panel, but still allow the container to run, due to explicit telling bitwarden to disallow insecure token, while the admin_token variable exists. ### Actual behaviour Using the environment variables `-e ADMIN_TOKEN=""` AND `-e DISABLE_ADMIN_TOKEN=false` gives me the error about either removing/filling the admin_token