Replies: 1 comment 10 replies
-
|
The entered token is trimmed so if it orginally started or ended with whitespace characters the login will fail. Line 237 in d626ea8 Not sure if there are other known issues. |
Beta Was this translation helpful? Give feedback.
10 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Prerequisites
Vaultwarden Support String
I’m migrating an existing self-built Vaultwarden installation to Docker on Windows.
A plain text ADMIN_TOKEN works correctly and allows access to /admin.
However, when I use a hashed Argon2 token generated with: /vaultwarden hash
the admin login always fails with: [vaultwarden::api::admin][ERROR] Invalid admin token.
What I have verified:
Example compose configuration:
environment:
ADMIN_TOKEN: $$argon2id$$v=19$$m=19456,t=2,p=1$$...
Inside the container the variable resolves correctly to:
$argon2id$v=19$m=19456,t=2,p=1$...
Is there anything specific required when using Argon2-hashed admin tokens in Docker Compose on Windows, or any known issues with this setup?
I’m coming from “built from source/w rust” to Docker container. I just copied the token from .env to the compose file.
Vaultwarden Build Version
Latest
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
caddy
Host/Server Operating System
Windows
Operating System Version
Windows 11
Clients
Desktop
Client Version
No response
Steps To Reproduce
Already described.
Expected Result
Already described.
Actual Result
Already described.
Logs
Screenshots or Videos
No response
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions