Workspace App not able to use the Gateway

Do you know what the client want to do exactly with the Gateway?

Regards

Do you know what the client want to do exactly with the Gateway?

Regards

Client wanted to be able to launch Remote sessions using the workspace app connected to Devolutions Server,instead of redirecting him to RDM or Launcher.

Hello,
Thank you for the details, but just to manage customer expectations, the only thing we could eventually do is embed a web-based session into Workspace. This means that we will never have the same user experience in Workspace, and it's definitely not a goal to do so.

Regards

Hello,
Let me expand on this feature request a little further. Data source in our case is Devolutions Hub Business, and the idea is to streamline our end-user access experience across supported sessions.
Take a look please at the attached screenshots, one is from our end-user using standard web browser (which currently supports launching common session via RDM, Launcher and Gateway), the second one is from our end-user using Workspace (which supports launching common session via RDM, Launcher but not Gateway), having this ability implemented even through embedded web session would be tremendous for us, especially since we require some session to go through Gateway. Not to mention smooth access to RDP, VNC, SSH via HTML5 via common interface.

You may ask why do we prefer Workspace? Single lightweight, supports right-click actions, embedded authenticator, offline access for password entries, Windows/Mac/Mobile app, supports sap plug-in (via intermediary launcher(hub web portal doesn't support that)). Please note that for our professional/power users we use RDM :)

Hello,

Thank you for your clarifications and the valuable feedback you provided. As part of our roadmap for the next major release (2025.2.0), we are planning to introduce support for opening sessions through the Gateway. While there are a few minor details that still need to be finalized on our end, the planned implementation is expected to include the following protocols:

• RDP
• VNC
• SSH
• Telnet
• PowerShell
• Web

As David mentioned in his last post, these implementations are simply intended to provide a fast and easy way to use these sessions. The best user experience remains with RDM and Launcher, and the goal of this initiative is not to replace either RDM or Launcher.

Best regards,