RDM Jump not working in 2024.1.7 Beta
Hi All,
I'm testing the beta version 2024.1.7 to see if the new cyberark datasource is a nice feature for us.
However, today I found out, that "Jump" is not working. I'm running the 2024.1.7.0 beta as a portable, separate instance from the ZIP file, alongside the installed version.
If I start a jump session, the initial jump is made, but further nothing happens
Even if I pre-login in the jump server, and start RDM, it won't work.
Tested on multiple connections.
Then start the 'installed' version of RDM on my workstation (2023.3.39.0) and it works flawlessly, same datasource, same connections.
Note that on the jumpservers, also 2023.3.29.0 is installed.
Regards, Ben van Zanten
All Comments (4)
Hi Ben,
Looking forward to any feedback on the CyberArk data source. A KB should be available soon to help you navigate the configuration.
As for Jump with 2024.1 you are correct we also found the issue last night just as I had a foot out the door. From what I’ve seen it looks like an issue with invalid characters being pushed with the XML, I’m guessing an BOM (byte order mark). We will investigate.
Stéfane Lavergne
Thanks Stefane for your reply.
So I was just ahead of you with finding this jump feature ;-)
Regarding testing with CyberArk datasource we're very interested in this feature. The KB is highly needed specifically in terms of requirements and how to have those met.
I already had the first requirement hurdle when 2024.1.x requires a newer version of .NET desktop or something.
but now it is complaining that I don't have a CyberArk license configured. and I have no idea how or where to configure the CyberArk license in the cyberark datasource. We HAVE a CA license...
Maybe it has to be configured within CyberArk (I guess) but that is another team. so I need to know what they need to configure within CyberArk, in order to make RDM 2024.1 work. I guess the license, but maybe a specific vault, or other objects as well?
Regards, Ben van Zanten
Hi Ben,
The jump issue has been resolved and will be in the next release. Requires you update both client & jump host RDM installs. It wasn't a BOM issue but rather an encoding issue (Unicode vs Utf8).
As for CyberArk, I'm, still working on the KB. here is a (very) high level overview.
Introduction
Remote Desktop Manager (RDM) v2024.1 introduces the CyberArk data source (preview). Connect directly to your CyberArk server eliminating the need for a SQL or DVLS data source to host the CyberArk dashboard session. RDM now acts as a front end, a dashboard if you like, to your CyberArk server allowing you to launch your sessions with ease. Leveraging the power CyberArk and RDM without the added complexity of a DVLS or SQL Server data source.
- Requires v2024.1 & CyberArk v14
- On first connect, RDM will:
- Import a Platform (Devolutions Remote Desktop Manager)
- Create a Safe (RDM_Settings)
- Create an account (DataSourceSettings)
- Note this assumes you have the rights to perform the steps above
- If you have "Add Safe" privilege, you are considered "admin" in RDM and can modify the System Settings & License
- Assign a license (in RDM > Administration > Licenses)
- RDM can now list your CyberArk safes & connect using accounts
Stéfane Lavergne
Hi Ben,
Here is the link
https://docs.devolutions.net/rdm/data-sources/data-sources-types/cyberark-data-source/
Best regards,
Stéfane Lavergne