RDM - Select Credential from User Vault not working anymore while opening session

Resolved

RDM - Select Credential from User Vault not working anymore while opening session

avatar

Hi,

We’re experiencing an issue after the latest updates of RDM and DVLS.

When opening a connection and selecting "Open with parameters > Open (select credentials)", and then choosing credentials from the User Vault, the connection fails.

A credential prompt appears, but it requests the password for a different user account than the one selected from the User Vault.

RDM Version: 2025.2.13.1
DVLS Version: 2025.2.2.0

All Comments (7)

avatar

Hello,

Thank you for reaching out regarding this matter.

We released a new version this morning (2025.2.14.0) that specifically addresses this issue. I recommend updating RDM to the latest version and testing it to see if the problem is resolved.

Please let me know if the issue persists.

Best regards,

Jacob Lafrenière

avatar

I am having a similar issue on macOS. Is there an update coming for macOS?

RDM Version 2025.2.6.8
DVL 2025.2.2.0

avatar

Hello,

Thank you for reporting this issue on MacOS.

I was able to reproduce the issue you are experiencing as well on the MacOS side. I will report this bug to the development team, and they will begin working on a fix soon.

I will follow up with you as soon as a fix is deployed in a future update.

Best regards,

Jacob Lafrenière

avatar
Hello,

Thank you for reaching out regarding this matter.

We released a new version this morning (2025.2.14.0) that specifically addresses this issue. I recommend updating RDM to the latest version and testing it to see if the problem is resolved.

Please let me know if the issue persists.

Best regards,


@Jacob Lafrenière
Hi Jacob,

Thanks for your response!
We tested the functionality after the update to version 2025.2.14.0, but unfortunately the problem is still there.

avatar

Hello,

Thank you for your follow-up.

Apologies for the confusion, this was my mistake. We recently resolved a very similar issue, which led me to believe it was the same case. However, after further investigation, I was able to reproduce the issue you’re experiencing.

I’ve reported this bug to our development team, and they will begin working on a fix. I’ll keep you updated and follow up with you as soon as the fix is included in a future update.

Best regards,

Jacob Lafrenière

avatar
Hello,

Thank you for your follow-up.

Apologies for the confusion, this was my mistake. We recently resolved a very similar issue, which led me to believe it was the same case. However, after further investigation, I was able to reproduce the issue you’re experiencing.

I’ve reported this bug to our development team, and they will begin working on a fix. I’ll keep you updated and follow up with you as soon as the fix is included in a future update.

Best regards,


@Jacob Lafrenière

Hi Jacob,

We installed the new version (2025.2.16.0) and this issue is now fixed for us.
Thanks for the quick fix!

Best regards,
Nick

avatar

Hello,

Thank you for the follow-up.

I will go ahead and mark this topic as resolved.
Please feel free to reply here if the issue arises again.

Best regards,

Jacob Lafrenière