mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-02 22:57:18 -05:00
Yubikey OTP not persistent after re-creating Docker container #1247
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1247
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mtnakayama on GitHub (Apr 3, 2022).
Yubikey OTP not persistent after re-creating Docker container
Yubikey OTP is not persistent when destroying and re-creating a vaultwarden docker container, even when the
/datavolume is mounted.Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
docker-compose.yml
Note:
YUBICO_CLIENT_ID,YUBICO_SECRET_KEY, andADMIN_TOKENare provided in my.envfile.Steps to reproduce
docker-compose up.docker-compose down.docker-compose up.Expected behaviour
I should be able to log in with the Yubikey OTP I set up before.
Actual behaviour
The web app says "Given Yubikey is not registered" when I try to use the Yubikey OTP as two-step authentication.
Troubleshooting data
When I try to log into the newly created container, I get the following error:
@BlackDex commented on GitHub (Apr 3, 2022):
I see you didn't configured the DOMAIN variable (Or you removed it), but that is really needed for MFA Tokens.
Also could you please provide the output of the
Support Stringwhich you can generate via the admin panel/admin/diagnostics?And.. What if you do not shutdown the the container, can you then logout and back in?
And, what happens if you try it again right after the first failed attempt?
@mtnakayama commented on GitHub (Apr 3, 2022):
I do have the
Domain URLvariable correctly configured underGeneral Settings. Under the diagnostics page, it saysDomain configuration [Match] [HTTPS]. (I believe the domain variable is automatically censored for the support string.) Is there more I need to configure?Here's the support string copied from
/admin/diagnostics:Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
Yes, I can log in using Yubikey OTP as many times as I want after I set it up. I only get these issues after I destroy and re-create the container.
Trying again after the first failed attempt results in the same error.
@BlackDex commented on GitHub (Apr 5, 2022):
Could you try this also with the current
testingtagged image please. Sand see if that also behaves the same. I do suggest to create a backup of the database btw before you do this.@BlackDex commented on GitHub (Apr 12, 2022):
@mtnakayama any update on this?
@BlackDex commented on GitHub (Apr 23, 2022):
Going to close this issue as there is no response and until now nobody else reported an issue like this.
If this issue still occurs, please re-open with the an answer the the above questions and more details.