Issue with 1Password and BitWarden integration

Hello,

Thank you for reaching out to us regarding this,

Could you confirm which type of data source you are using?
https://docs.devolutions.net/rdm/data-sources/data-sources-types/

You mention that you are having this issue with the first launch. Am I correct in assuming subsequent launches are working as expected?

If you go under "Help" -> "Application Logs" are there logs generated relating to this error? If so can you provide us the full logs.

Let me know,

Best regards,

I am using Microsoft SQL Server (Express) on my laptop for my database and datasource. If I do not change the credentials the second launch throws the same errors. After changing the credentials then it works by double-clicking but not the Open Session button - it seems that is dead.

I will check for logs to see and attach.

@Samuel Dery Here are the error logs for the problem, which started yesterday after the upgrade on Wednesday to the 2025.3 release.

Hello,

Thank you for your reply,

I see, I can reproduce the behavior, I have opened a case with our development team which I will link to this topic,

We will keep you updated with any news we have regarding this,

Best regards,

Perfect. Glad this helped, and hopefully we can get these issues resolved in the next release. I will keep an eye on this thread.

Please also ensure the Open Sessions button is fixed too as that is not working at all either. The only way for me to launch a session is double-clicking.

It is funny I have another system that has the same beta build and the open sessions button works. But it does not have 1Password or Bitwarden integrations.

Hello,

I'm currently working on the issues, but I have a quick question: what mode are your 1Password entries set to — “Web connector” or “Linked to a local file”?



I’ll keep you updated on the progress.

Regards,

Léon Le Brun

@Léon Le Brun - I have it set to Web Connector as 1Password does not use local files anymore that I am aware of. BitWarden is different but similar problems. Also please ensure the Open Session button issue is looked at. Not sure if related with the other issues maybe.

Hello,

Thank you for the quick reply.

There’s something I’d like to confirm with you regarding the error you shared in your initial comment:


Can you confirm whether this error appears with both 1Password and Bitwarden? On my end, I was able to reproduce it with Bitwarden (and that issue has since been fixed), but I haven’t been able to trigger the same error with 1Password. I did fix an unrelated issue with 1Password, but I’d like to make sure this addresses the problem you’re experiencing.

Also, the Open Session issue has been noted and will be looked into.


Regards,

Léon Le Brun

@Léon Le Brun - Yes, my apologies, that error was for BitWarden, not 1Password. The other message I posted was 1Password. Still not sure what is wrong with the Open Sessions button, as I have RDM installed on another system, Windows 10, and it works.

Hello,

I see — thank you for the confirmation. However, it looks like there’s an issue with the second screenshot in your initial comment. Could you please resend the message related to the 1Password issue?

That would help us investigate further.


Regards,

Léon Le Brun

@Léon Le Brun - this is the other message with 1Password that comes up regardless of how many times you try the connection. I need to switch it to KeePass to fix and use RDP.

@Léon Le Brun - tested the new minor release that came out but same issues with 1Password, BitWarden and the Open Session button not working.

@Léon Le Brun @Samuel Dery -- any updates on these issues and getting them fixed? I tested the latest minor release but still have all three issues.

Hello,

We currently have our developer in charge of the Bitwarden and 1Password integrations looking into this. He was able to reproduce the issue (as well as an additional one you didn't encounter) and is working on this today. We are aiming to have this resolved for our next 2025.3 version (which should be the stable release candidate). In the mean time I would encourage you to stick with the 2025.2 version if this is blocking, as I believe the issue doesn't occur there.

Regards,

Hello,

We currently have our developer in charge of the Bitwarden and 1Password integrations looking into this. He was able to reproduce the issue (as well as an additional one you didn't encounter) and is working on this today. We are aiming to have this resolved for our next 2025.3 version (which should be the stable release candidate). In the mean time I would encourage you to stick with the 2025.2 version if this is blocking, as I believe the issue doesn't occur there.

Regards,

@Hubert Mireault
If I downgrade to 2025.2 how does that work with the DVLS 2025.3? When going to 2025.3 release this was updated so it is backward compatible with 2025.2?

So I exported my entries from SQL in 2025.3 and downgraded to 2025.2 with a new DB and imported entries. But now, nothing connects when I click Open Session, or double-click an entry; it will not connect via RDP at all. So I am stuck, and it looks like I will need to continue with the broken 2025.3 to at least make this usable. Not happy.

Hello,

For the compatibility between DVLS 2025.3 and RDM 2025.2, I checked with the DVLS team lead, and while it's not recommended to stick with 2025.2, it should still be supported for the most part. New features from 2025.3 will not work with that client, and if you are using Privileged Access there might be certain unavailable endpoints, though all of the crucial ones should still be available and work fine.

Are you using both SQL Server and DVLS as datasources, or do you mean you did a manual export of the data in your SQL Server where DVLS is hosted, and reimported it? I will ask one of our support agents to open a case with you in high priority as it sounds like you might be unable to work after this manipulation.

Regards,

Hello,

For the compatibility between DVLS 2025.3 and RDM 2025.2, I checked with the DVLS team lead, and while it's not recommended to stick with 2025.2, it should still be supported for the most part. New features from 2025.3 will not work with that client, and if you are using Privileged Access there might be certain unavailable endpoints, though all of the crucial ones should still be available and work fine.

Are you using both SQL Server and DVLS as datasources, or do you mean you did a manual export of the data in your SQL Server where DVLS is hosted, and reimported it? I will ask one of our support agents to open a case with you in high priority as it sounds like you might be unable to work after this manipulation.

Regards,

@Hubert Mireault
Yes I exported to RDM format the data from my SQL Server DB - all entries, passwords, etc. which was on 2025.3 with DVLS 2025.3. I then uninstalled 2025.3 version and cleaned up files/directories. Installed 2025.2 and created a new SQL Server DB for use with the program. I then imported the exported RDM file to get all my connections back and credentials but now the program is useless to use nothing works. It fixes the 1Password issue but no connections open with Open Session button or double-click. So I was stuck. I removed 2025.2 and went back to 2025.3 with my other SQL Server datasource and now can at least use my RDP connections once I change them to use KeePass creds intead of the problem apps.

Hello,

Thank you for your reply,

I would like to have a remote session with you to have a look at your Open Session issue. To do so, I would need to open a case.

Would the email used for your Forum Account be the correct one to use?

If not, let me know and I can send you a private message so that you can provide me with the correct email to use.

Best regards,

Hello,

Thank you for your reply,

I would like to have a remote session with you to have a look at your Open Session issue. To do so, I would need to open a case.

Would the email used for your Forum Account be the correct one to use?

If not, let me know and I can send you a private message so that you can provide me with the correct email to use.

Best regards,

@Samuel Dery
Is this for the 2025.2 issue? If so I have gone back to 2025.3 and changed connections to use KeePass until the other apps are fixed or is it for the Open Session issue with 2025.3? Let me know.

Hello,

Thank you for your reply,

You mentioned that you were having an issue with the Open Session on both the Beta version 2025.3 and when you reverted to 2025.2. Is it now working as expected when using the Open session on 2025.3?

Let me know,

Best regards,

Hello,

Thank you for your reply,

You mentioned that you were having an issue with the Open Session on both the Beta version 2025.3 and when you reverted to 2025.2. Is it now working as expected when using the Open session on 2025.3?

Let me know,

Best regards,

@Samuel Dery
It is still broken in 2025.3

@Samuel Dery -- as noted the Open Session button is still broken in 2025.3 after going back to this to get RDP sessions to work. I can wait on the next release to fix the 1Password/BitWarden issues but can we check the Open Session button? It works on another system that I have with 2025.3 but the only difference is that does not use SQL Server for datasource and it is Windows 10 not 11. OS should not make a difference here though.

Hello @cchilderhose ,

Thank you for your reply,

Can you confirm that the email used for your Forum account is the correct one to use for the case?

I will create this case and send you a link to schedule a remote session as mentioned,

Best regards,

@Samuel Dery - yes you can use the email associated to the forums for the case and link to remote session.

Hello,

We have successfully resolved the 1Password and Bitwarden issues. The correct behavior will be available in the upcoming 2025.3 version.

Regards,

Léon Le Brun

Hello,

We have successfully resolved the 1Password and Bitwarden issues. The correct behavior will be available in the upcoming 2025.3 version.

Regards,

Léon Le Brun

@Léon Le Brun @Samuel Dery @Hubert Mireault

I installed the 2025.3 release and still have the same problem with the 1Password credentials being used so it is not fixed. I am testing BitWarden now.

@Léon Le Brun @Samuel Dery @Hubert Mireault

I have actually fixed the 1Password issue as well as BitWarden. I had to edit each of the credentials I had set up for both integrations and select the same credential from the app again, then Save the entry in RDM. Once I did that connections started to work.

@Samuel Dery -- FYI for you - the Open Session button now works in the tree without issue on the new 2025.3 release. The one we tested on our remote session so all good now. :)

Hello,

Thank you for your reply,

I'm glad to hear this is now working.

Did your colleagues also encounter the same error message? I'm also wondering if the behavior reoccurred since you changed the entry Properties?

Let me know,

Best regards,

Hello,

Thank you for your reply,

I'm glad to hear this is now working.

Did your colleagues also encounter the same error message? I'm also wondering if the behavior reoccurred since you changed the entry Properties?

Let me know,

Best regards,

@Samuel Dery

I have not seen the issue since editing and saving the entries. Not sure why that was required but glad it is working as well as the Open Session button again. :)

Hello Chris,

Thank you for your reply,

I see, I will consider this thread resolved for now,

If the problem returns feel free to let me know,

Best regards,