micheleschelfi

Hi @micheleschelfi,

Thank you for reaching out, it is not currently planned to support generic OIDC/SAML SSO in Devolutions Server but we have received the request previously. If you may disclose, which identity provider do you use? We might have more chances of supporting that specific provider than a generic one.

Cheers,

Hi @Luc Fauvel, thank you for explaination

We are currently using Keycloak (RHBK), which supports both OIDC and SAML

Thanks

Good morning,

I am configuring a new DVLS 2026.2 environment.

Our company needs to implement an SSO authentication process to allow users to authenticate to the Devolutions Server datasource from Remote Desktop Manager (RDM).

From the options currently available in the administrative settings, I can see dedicated configuration sections for Okta and PingOne. Unfortunately, we do not use either of these platforms and would need the ability to configure a generic OIDC or SAML client instead.

Ideally, this integration should also support the import and synchronization of users and groups.

Is there already a way to achieve this today?

If not, would it be possible to consider implementing this functionality in one of the upcoming releases?

Thank you.

@Michel Audi

Thank you for your reply. I’m still not entirely clear about the network flow and architecture regarding the recording gateway.

Does this gateway need to be able to reach the remote servers? I don’t fully understand what you mean by “the Gateway used for recording can be different from the one used to establish the connection.”

Is it possible to have a single Gateway object, located in the same network as DVLS without direct access to the target servers, and use it exclusively for recordings?

The end user will have direct access from their workstation to the Devolutions infrastructure and will only use RDM.

Thank you.

Good morning,

I am currently working on a POC to migrate from RDM + SQL to a Devolutions Server + RDM solution (Devolutions Server will be used solely as a data source; web access is not planned, and everything will go through the RDM client).

I would like to configure session recording for RDP and SSH. While reviewing the documentation, I noticed that using Devolutions Gateway is required. Are there any alternative solutions?

At the moment, I am working on deploying DVLS in a Kubernetes infrastructure. I have already configured the environment with 3 separate pods and an external SQL Server hosted on a Windows server.

Deploying the Gateway could be problematic because the company needs to connect to dozens (or even hundreds) of segregated customer environments. Our current operating model relies on dedicated VPN connections, and introducing an additional agent like Devolutions Gateway would be difficult.

My question is the following:

Is it possible to configure a recording service that saves session data to a specific network path without necessarily going through the Gateway? (for example, a path within the database server environment)

Additionally, is it possible to configure a retention policy with automatic deletion for the recording files?

Thank you in advance for your support.

Hello,

I’m writing to ask whether the integration of AWS Console sessions with Amazon’s internal authentication system (AWS SSO) is currently on the roadmap or already available.

In our company, we need to manage multiple AWS tenants. To access them, we typically use AWS SSO, which allows a defined user to assume the corresponding IAM roles associated with each tenant.

From what I’ve seen, the current RDM session only supports connecting to a specific tenant using an internal IAM user for that tenant.

Will it be possible to manage access to multiple tenants via AWS SSO in the future?

Thank you!