mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-11 01:10:09 +03:00
Bitwarden 2023.8.2 no longer works with Vaultwarden #743
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 @sjansen1 on GitHub.
Subject of the issue
Bitwarden 2023.8.2 no longer works with Vaultwarden. After a Bitwarden Update on Windows and Linux, Bitwarden no longer allows login via Pin, after logout and login, bitwarden starts an assisstant to setup SSO and asks again for a new master key.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
1.29.1
Vaultwarden was installed via Podman.
Bitwarden Linux Flatpak and Windows Store Version 2023.8.2
nginx-1.20.1-1.module_el8 (AlmaLinux)
Postgresql-server-12.15-1.module_el8
Steps to reproduce
Vaulwarden is startet via Podman as a User and Userspace systemd. Like everytime.
Expected behaviour
Login via Bitwarden Desktop (Linux and Windows)
Actual behaviour
Login via E-Mail and Masterpassword is successful, but it does not open the vault, instead a SSO Setup Wizzard starts and asks for a new Masterpassword, entering it brings an error Messsage in Bitwarden. Browser extension still works same as vaultwardens webvault.
Troubleshooting data
Sorry this is a german screenshot, this popups right after login with email and password, of course the server was set to self hosted with url redirecting to vaultwarden, all this works fine until the Bitwarden update.
@stefan0xC commented on GitHub:
Should be fixed by #3813 (can you test with
testingonce the current build is complete)?@BlackDex commented on GitHub:
Is already fixed in the current main code.
New
testingtagged builds are currently being created.