RDM 2021.2.X appears to be ignoring Devolutions Server version management settings
RDM 2021.2.X appears to be ignoring Devolutions Server version management settings
Tested with :
RDM Version : 2021.2.27.0
Devolutions Server Version : 2021.2.14.0, 2021.2.10.0 & 2021.1.20.0
It looks like RDM version 2021.2 is bypassing the version management rules on DVLS. When connecting to a datasource with an RDM version that is higher than the accepted version in the DVLS version management settings, the error message appears stating the it cant connect but, after selecting ok in the error box, the connection will go through. Once you are connected tot he vault, this also occurs when you attempt to make any changes to the vault. When adding an entry it will prompt twice that it is not allowed, but the new entries will go through.
How to replicate the issue
- On DVLS 2021.2.14.0 set the Maximal Version under Version Management to 2021.2.20.0
- Set the "Maximal version custom message" to "Not Supported"
- Connect to the datasource with RDM version 2021.2.27.0
- Select ok on any 'Not supported' messages
All Comments (6)
Hello,
Thank you for contacting us on that matter!
To help us determine the exact cause of the issue, I would be curious to verify if the issue also occurs with the Version Management menu in RDM, or if it is exclusive to when the maximal version is configured in the Devolutions Server web interface.
The Version Management menu can be found in RDM under Administration > System Settings > Version Management.
Best regards,
Gabriel Degrandpré
I can confirm that setting the Maximal Version via RDM rather than the web interface also seems to have no different effect.
Hello,
Thank you for your reply,
We will test this on our end to see if we're able to reproduce this behavior.
Best regards,
Samuel Dery
Hello,
Thank you for your patience,
I would like to confirm if the user you're attempting to connect to the data source with is an administrator?
Let me know,
Best regards,
Samuel Dery
Yes the user that was attempting to access the vault was an administrator. I have not tested this on a non admin account.
Hello,
Thank you for your reply,
From my understanding, this is indeed the intended behavior with an "Administrator" account, you will receive the warning but will still be able to connect to the data source.
This is to ensure, you're not locked out of the data source if an incorrect version number is entered by mistake.
Let me know if this helps,
Best regards,
Samuel Dery