starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #203] Second organization collection is working incorrectly in Vault until log out/in is done by the owner #105

New issue

Closed

opened 2026-03-03 01:24:56 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:24:56 +03:00

Owner

Originally created by @shauder on GitHub (Oct 1, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/203

Starting with a fresh database to make sure I didn't have any lingering issues from previous testing.

Observations:
Create new account
Create new org

This seems to work as intended - I get a default collection and they show up

Create second org

This creates a default collection but it is without a name and does not show up in your collections (unable to decrypt) on applications outside web vault

Create new collection in first org

Seems to work and shows up in my collections

Create new collection in second org

Not seeing it show up in my collections and seems to also have trouble decrypting

Adding a credential to the second org and then adding it to one of the collections seems to work initially. After reloading the web-vault the credential is no longer able to be decrypted and is lost.

Originally created by @shauder on GitHub (Oct 1, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/203 Starting with a fresh database to make sure I didn't have any lingering issues from previous testing. Observations: Create new account Create new org * This seems to work as intended - I get a default collection and they show up Create second org * This creates a default collection but it is without a name and does not show up in your collections (unable to decrypt) on applications outside web vault Create new collection in first org * Seems to work and shows up in my collections Create new collection in second org * Not seeing it show up in my collections and seems to also have trouble decrypting Adding a credential to the second org and then adding it to one of the collections seems to work initially. After reloading the web-vault the credential is no longer able to be decrypted and is lost.

kerem

2026-03-03 01:24:56 +03:00

closed this issue
added the
bug

troubleshooting
labels

kerem commented

2026-03-03 01:24:57 +03:00

Author

Owner

@mprasil commented on GitHub (Oct 1, 2018):

This issue is weird, but it looks like there's something wrong in the client data when you create the second organization that causes the subsequent issues. If you create the second Organization and log off/log back in, everything seems to be working fine. The default collection shows up normally.

@mprasil commented on GitHub (Oct 1, 2018): This issue is weird, but it looks like there's something wrong in the client data when you create the second organization that causes the subsequent issues. If you create the second Organization and **log off/log back in**, everything seems to be working fine. The default collection shows up normally.

kerem commented

2026-03-03 01:24:57 +03:00

Author

Owner

@shauder commented on GitHub (Oct 1, 2018):

You are correct the second default collection from the second org seems to work fine after a web-vault refresh in the browser. This seems to break the second collection I created in that org if it was made before a full refresh of the web-vault.

@shauder commented on GitHub (Oct 1, 2018): You are correct the second default collection from the second org seems to work fine after a web-vault refresh in the browser. This seems to break the second collection I created in that org if it was made before a full refresh of the web-vault.

kerem commented

2026-03-03 01:24:57 +03:00

Author

Owner

@mprasil commented on GitHub (Oct 14, 2018):

Okay, so after some in depth testing it looks like this only shows up if websockets aren't configured properly - the Vault app will get confused on unexpected error trying to sync and this is how this whole issue seems to start.

I've submitted PR #221 to hide the websockets negotiation behind configuration option and have that off by default as it will break Vault unless users also make sure proxy is configured correctly.

@mprasil commented on GitHub (Oct 14, 2018): Okay, so after some in depth testing it looks like this only shows up if websockets aren't configured properly - the Vault app will get confused on unexpected error trying to sync and this is how this whole issue seems to start. I've submitted PR #221 to hide the websockets negotiation behind configuration option and have that off by default as it will break Vault unless users also make sure proxy is configured correctly.

kerem commented

2026-03-03 01:24:57 +03:00

Author

Owner

@mprasil commented on GitHub (Oct 15, 2018):

#221 is now merged, I think we can close this one. Images are just building.

@mprasil commented on GitHub (Oct 15, 2018): #221 is now merged, I think we can close this one. Images are [just building](https://hub.docker.com/r/mprasil/bitwarden/builds/btmucyxbckjewpmrw3rqttn/).

kerem referenced this issue

2026-03-03 01:28:05 +03:00

[GH-ISSUE #526] Unable to enable U2F auth with Yubikey (400 Bad Request) #332