Navigation pane opening behind content in 2026.3.9
The problem appears to be fix now. Thanks!
Navigation pane opening behind content in 2026.3.9
I just upgraded from 2026.3.8 to .9. This fixed one issue for me but create a larger one. I usually have my navigation pane set to auto hide. When I need it, I click on the tab on the side of the RDM window and it pops up over my content (RDP session, web page). With 2026.3.9, the majority of the pane appears to render behind the main content (RDP session, web page). I can see the header, as it is displayed in the tab bar above the content, but the rest of my entries are hidden. This didn't occur in 2026.3.8.
Issue with links in embedded web browser in 2026.3.8
I just realized that 2026.3.9 was released. I installed and it appears to have fixed my issue. Thanks for the quick fix!
Issue with links in embedded web browser in 2026.3.8
I use RDM with DVLS and Devolutions Gateway to access web pages in a restricted network. Since upgrading to 2026.3.8 a couple of days ago, some of these pages are unusable due to a change in how URLs are displayed when hovering over a link.
In 2026.2 and in most other browsers, when hovering over a link, it displays the URL at the bottom of the page floating over the content (a toast?). It doesn't change the size of the viewport so the page doesn't need to re-render. However, in 2026.3.8, when I hover over a link, it creates a full width status bar to display the URL. It's not hovering over the content, so the page has to re-render/re-flow. Some apps are filled with links and don't behave properly like this. For instance, PRTG is one of the main web apps that I access, and it is totally unusable now.
RDM prompting twice for credential
For most of my RDM entries, I have Credentials set to "find by name (user vault)" with an empty box next to it. This generally does what I want and pops up a credential selection window when connecting. However, on most, but not all, entries, it pops up the credential selection box twice. I just have to select the same credential twice and everything else works fine. I haven't been able to narrow down what the difference is between the entries that ask once and the entries that ask twice. Is there a way to make them all ask only once?
For context, I'm using DVLS and Gateway with all of these.
Duo SSO integration
Here's another visual example of how many other products handle groups with SAML integrations. This is a screenshot of the new group creation screen in Palo Alto Cortex XDR. Note the "Saml Group Mapping" field. They don't do any group syncing via SAML. An admin creates a group in Cortex and then maps that to an existing group in the SAML provider.

Duo SSO integration
We are using Duo SSO synced with our on-prem AD. We're not using Entra. We mostly authenticate with push notifications to the Duo Mobile app, with a few users using Webauthn. Our security team just launched a "passwordless" authentication initiative, which Duo can do with Duo SSO and their Universal Prompt feature.
My request would be at minimum to allow user authentication via Duo SSO Universal Prompt with either a custom Duo integration or a customizable generic SAML/OIDC option.
Group membership info would be a nice to have. For other applications, I'm able to pass group memberships via a SAML attribute like "memberOf". I then create matching groups in the application which match up with the groups in the SAML attribute. There is no importing of groups into the applications, just a mapping. For instance, this is how the Fortigate VPN Duo integration works.
I believe importing of groups is possible with a SCIM integration, but the above would be good enough for my needs.
Duo SSO integration
DVLS currently supports Duo as an MFA provider but not as an SSO provider. Integrating with Duo SSO provides more features (e.g. passwordless), more authenticators (e.g. passkeys), and a better user experience. We're moving to passwordless authentication, and the current integration will not support it. Duo SSO supports SAML 2.0 and OIDC, so generic support for those would also suffice.