Issue with Bitwarden Sync
RDM 2026.3.13.0
I created 3 entries in Bitwarden (personal vault).
The entries are present in Bitwarden, but they do not appear in RDM (using Bitwarden Sync).
As a test, I tried running the sync with a new folder as the destination (the “Passwörter” folder).
Then I get this message:
Recommended Answer
Hi Footless4468,
Quick update before you change anything else. I passed all of this on to our team, and they're now reviewing the change with the Devolutions Server team. It was made to fix a security issue, but they're looking at allowing synchronizers in the user vault again. I don't have a version or date yet, and I'll update this thread as soon as I know more.
So my suggestion for now is to keep using your old setup:
Your existing "Bitwarden Sync" in your user vault still runs, as your test showed. Keep it, and don't delete it or its "Bitwarden" folder.
Your RDP sessions can stay on "Nach Namen suchen (Benutzer-Tresor)" with admin-rdp. They keep finding the entry that this sync creates in your user vault.
The only limitation is that you can't edit that sync until this is sorted out.
Your new shared vault doesn't get in the way. You can keep it as a test or ask your admin to remove it. If you keep both syncs running, you'll have two copies of every item, so I'd only run one of them.
If you need to change your sync settings before then, the other options are still there: a Bitwarden credential entry named admin-rdp in your user vault, which your sessions would find by name, or "Verknüpft (tresorübergreifend)" pointing at the synced entry in your new vault.
About the filter: I'd still like to understand why E-… was synced. When you have a moment, could you reopen the sync in your new vault and send a screenshot of the Filter tab? Please also tell me whether a folder with items from "Mein Tresor" shows up after a sync.
Let me know how it goes.
Eduard Sepulveda Lopez
All Comments (12)
Hi Footless4468,
Thanks for the screenshots, they make it clear what is happening.
This is an intended change on the Devolutions Server side rather than a bug. For security reasons, synchronizers are no longer allowed in the user vault. A synchronizer connects out to an external service with stored credentials, and that kind of outbound connection has to live in a vault an administrator controls. This also explains your missing entries: your existing "Bitwarden Sync" sits in your user vault, so the server now refuses to run it, and nothing new is imported. Changing its destination folder fails for the same reason.
You have two options:
Move the synchronizer to a shared vault. Recreate the Bitwarden synchronizer in a shared vault where you have full access, ideally inside a folder with permissions restricted to you. The imported entries will then land there, and only you will see them. If you don't have a suitable vault, your DVLS administrator can create one for you.
Use the Bitwarden credential entry instead. If you only need your Bitwarden credentials in your sessions, you can use the Bitwarden credential entry type, which you can keep in your user vault. It looks up your Bitwarden credentials when you need them, so nothing has to be synchronized. Both entry types are described here: https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/bitwarden/
Once that is done you can delete the old "Bitwarden Sync" entry from your user vault, since it can no longer run there.
Let me know how it goes.
Eduard Sepulveda Lopez