Bitwarden Synchronizer syncs all entries even though only the personal vault has been selected
Hello!
Sure, here it is!

Best regards,
Markus
Bitwarden Synchronizer syncs all entries even though only the personal vault has been selected
Hello!
Bitwarden Synchronizer easily syncs the organization's vaults. But if I only want to sync the personal vault (to my personal Devolutions Server Vault), the entire Bitwarden organization will still be synced, regardless of my selection under "Filters".
We are currently using RDM 2025.1.34 and Bitwarden 2025.5.0
Can you reproduce the behavior?
Thank you very much and best regards
Markus
Devolutions Server LTS Environment
Thank you very much for the quick answer!
Does this mean that we can continue to expect at least security fixes for the older versions of Server, RDM or Gateway?
Thanks again!
Best regards
Markus
Devolutions Server LTS Environment
Hello!
We are considering using the LTS version of the Devolutions Server (next one based on 2025.X).
How does this work with the other dependent products like Remote Desktop Manager, Gateway, Workspace Plugin? I can't find an official LTS version there.
Do I simply have to install the corresponding "old" versions here? Will they at least still get security updates? Will these versions still be supported?
Is there an official strategy here? For example, the last major version of the previous year will become the LTS version?
Maybe there is already a documentation about it...
Thank you very much for the help!
Bitwarden Synchronizer - Missing Field
Hello Hubert!
I am impressed with how quickly the feature was implemented and would like to express my gratitude for that!
Best regards,
Markus
Bitwarden Synchronizer - Missing Field
Hello Hubert!
Thanks for the quick reply!
Yes, that seems to be the best solution for that.
Regards
Markus
Bitwarden Synchronizer - Missing Field
Hello!
So far, we have been using Bitwarden as a password vault. For the switch to Devolutions, we use the Bitwarden Synchronizer to get the entries (import via CSV only leads to unusable data). However, we lose important information, which is in Bitwarden in the "Notes" field and obviously cannot be synchronized - we use "session/Website" entry as target to not lose URL information.
Are there any plans to be able to synchronize "notes" field as well?
Thank you very much
Markus
Version in use:
Devolutions Server 2024.3.4.0
Devolutions RDM 2024.3.18.0
Bitwarden 2025.1.0 (Client 2025.1.1)
Vault Owner und Vault Administrator - effektive Berechtigungen
Hallo!
Leider kann ich weder in der Doku noch hier im Forum klare Infos zu folgenden Thema finden:
Ich kann in Devolutions Server auf Vault-Ebene Owner sowie Administrators setzen. Allerdings lässt sich nicht klar herausfinden, welche Rechte oder Möglichkeiten mit den jeweiligen Rollen einhergehen.
Gibt es hier irgendwo einen Überblick? Wäre für einen Link dankbar, oder eine kurze Erläuterung dazu.
Vielen Dank!
Devolutions Password Manager App gets HTTP ERROR 500 after MFA Authentication
Hi Erica!
Thank you very much for your fast response!
I'm going to upgrade next week. Our Devolutions setup is still in pre-production state, testing with key users ;-)
I'll give feedback after upgrading.
Best regards,
Markus
Devolutions Password Manager App gets HTTP ERROR 500 after MFA Authentication
Hi!
Yes, I mean Domain SSO.
Workspace 2024.1.0.3
Server 2023.3.14.0
RDM 2023.3.39.0
Token Lifetime is not related to the error 500 problem. From time to time, i'm able to logon per SSO without MFA - after 12 hours, regardless if RDM or Workspace.
Thanks alot!
Devolutions Password Manager App gets HTTP ERROR 500 after MFA Authentication
Hi there!
I'm new and thats my first post ;)
We are going to use the Workspace app in combination with Devolutions Server. We activated SSO as well as MFA (TOTP or YubiKey).
MFA works fine with Remote Desktop Manager. But with Workspace App (Chrome Plugin) we got an Error 500 after MFA authentication.
Logs on Devolutions Server says we authenticated successfully.
After ~2 Minutes of waiting, we refresh the "Error 500" Page, and thats it: we are successfully logged in!
Every time this happens, i'll get a strange email about it:
The following error
was received by at 03/06/2024 07:14:42
Error:
InvalidOperationException
- The specified principal was rejected because the mandatory subject claim
was missing. at
OpenIddict.Server.OpenIddictServerHandlers.ValidateSignInDemand.HandleAsync(ProcessSignInContext
context) at
OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at
OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandler.SignInAsync(ClaimsPrincipal
user, AuthenticationProperties properties) at
Microsoft.AspNetCore.Authentication.AuthenticationService.SignInAsync(HttpContext
context, String scheme, ClaimsPrincipal principal, AuthenticationProperties
properties) at
Devolutions.Server.OAuth.Handler.VerifyRequestHandler.HandleAsync(HandleVerificationRequestContext
context) at
OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at
OpenIddict.Server.OpenIddictServerHandlers.Device.HandleVerificationRequest.HandleAsync(ProcessRequestContext
context) at
OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at
OpenIddict.Server.OpenIddictServerDispatcher.DispatchAsync[TContext](TContext
context) at
OpenIddict.Server.AspNetCore.OpenIddictServerAspNetCoreHandler.HandleRequestAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext
context) at
Devolutions.Server.Middleware.LegacyTokenParserMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.OAuth.Middleware.OAuthTokenParserMiddleware.InvokeAsync(HttpContext
httpContext) at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext
context) at
Devolutions.Server.Middleware.ReferrerPolicyMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.StrictTransportMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.XContentTypeOptionsMiddleware.InvokeAsync(HttpContext
httpContext) at
Devolutions.Server.Middleware.XFrameOptionsMiddleware.InvokeAsync(HttpContext
httpContext) at Devolutions.Server.Middleware.CSPMiddleware.InvokeAsync(HttpContext
httpContext) at
Serilog.AspNetCore.RequestLoggingMiddleware.Invoke(HttpContext httpContext)
at
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware
middleware, HttpContext context, Task task) --- Default
Source:
OpenIddict.Server Also, I'm a bit confused about the token lifetime. I've set it to 12 hours. But it seems to be a more random value - not infrequently i can login without MFA the next day!
I hope you can help me with the issues and I am already very grateful!
Best regards
Markus