mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-10 17:23:04 +03:00
Yubikey OTP failure #302
Reference in New Issue
Block a user
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 @pquantin on GitHub.
Vaultwarden Support String
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
Vaultwarden Build Version
1.32.5-d7adce97
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx on Synology NAS
Host/Server Operating System
NAS/SAN
Operating System Version
NAS Synology 7.2.2
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Try to use Yubikey OTP for 2nd step authentication.
Expected Result
Yubikey OTP succeeds.
Actual Result
The Vaultwarden logs shows an error regarding an invalid padding. This used to work in the past (the Yubikey is registered in my account and was working fine the last time I tried it some time ago). Moreover the Yubikey works fine with https://demo.yubico.com/otp/verify
Logs
Screenshots or Videos
No response
Additional Context
No response
@pquantin commented on GitHub:
I tried doing that before filling the issue and I get the same error. This is a Yubikey 5C NFC. No idea how to move forward, especially as it was working fine before.
@BlackDex commented on GitHub:
I'm using the same version
@pquantin commented on GitHub:
Any extra info I could provide to move forward? I guess it could be related to #5248 but I do not have anymore the previous docker image to test against.
@pquantin commented on GitHub:
Some extra info: reverting to 1.32.5 tag works fine. But using 1.32.5-d7adce97 (latest testing image) fails with the error previously mentioned.
@BlackDex commented on GitHub:
Seems to work just fine for me using a YubiKey-5C via USB-C on my Laptop.
Same via my Android Phone.
Try to remove the key and add it again and see if that helps.
@axi92 commented on GitHub:
I had the same issue, I did not find anything in the changelog. But thanks to the issue I was able to fix it by adding a '=' at the end =)
@BlackDex commented on GitHub:
Cool. Great that it worked.
Most of the time those extra
=padding chars are not that big of an issue. But that is mostly for ASCII data.Since these keys are binary it could cause weird issues if not padded correctly.
Assuming or fixing it automatically could also cause strange issues sometimes.
@pquantin commented on GitHub:
Thanks a lot, that helped. BTW great work and dedication for this project, this is greatly appreciated 👍
@BlackDex commented on GitHub:
I think you need to add one or two
=signs to yourYUBICO_SECRET_KEYvalue.It might be it's stripped somehow or not added for some reason.