devolutions47

Hi there,

We are happy to release the DVLS 2026.1 BETA version.

Please make a backup before performing the upgrade, and we strongly recommend you install it in a test environment first - https://docs.devolutions.net/server/kb/how-to-articles/create-server-staging-instance/

Console download(.exe):

https://cdn.devolutions.net/download/Setup.DVLS.Console.2026.1.1.0.exe

Offline package (.zip):

https://cdn.devolutions.net/download/RDMS/DVLS.2026.1.1.0.zip

Upgrade procedure:

https://docs.devolutions.net/server/getting-started/installation/upgrade-server/

If you are using a client (RDM, PowerShell, etc.), version 2026.1 is required for this DVLS version

NEW FEATURES

• Core - Added custom vault dashboard widgets with drag-and-drop reordering

• Core - Added Just-in-Time (JiT) access for SSH (sudo) sessions

• Core - Added new Contractors account type with expiration date support

• Core - Added vault priority sorting

• Core - Admins can create preset dashboards for users

• Core - Licenses can now be purchased directly within DVLS

• Core - Users can now request a trial directly from the application

• Core - Users can now request sudo access when requesting checkout

• Gateway - Added RDP credential injection for more secure session launches

• Gateway - Added traffic event logs to privileged session monitoring

• PAM - Added MongoDB provider support

• PAM - Added PowerShell session recording

• PAM - Added UI to assign and manage risk levels for roles

IMPROVEMENTS

• Core - Added launch links on connections for quick session sharing

• Core - Added OTP support for linked external vaults

• Core - Admins can set the default behavior for automatically checking in PAM accounts when closing entries

• Core - Entra ID now enforces secret expiration with banner and email warnings

• Core - Entry security settings now use inherited values by default

• Core - Error reports now include connection type details

• Core - Improved performance for access requests in RDM

• Core - Linked vaults can now point to entries in the same folder

• Core - Public API now supports CRUD operations for folders and vaults

• Core - Renamed Log Retention Policies to Database Retention Policies and added retention options for connection history, remote sessions, and traffic events

• Core - Simplified license assignment in data sources

• Core - Synchronizers now support scheduling by hour

• Core - Tags can now be used with inheritance rules

• Core - Users can now configure multiple MFA methods at once

• Gateway - Renamed "Virtual Gateway" to "Gateway ruleset"

• Gateway - Sessions can now be recorded on a different gateway than the launch gateway

• PAM - Added "Create folder" option when importing PAM accounts

• PAM - Added "Skip TLS validation" option in PowerShell provider settings

• PAM - Improved error message when no provider is specified on a PAM account

• PAM - Renamed "Scan" to "Account Discovery"

• Web Client - Multiple UI improvements

• Web Client - Updated dark theme

FIXES

• Core - Fixed an error occurring when too many vaults were present

• Core - Fixed duplicate vault cards appearing on the dashboard

• Core - Fixed login loop when access URI contained uppercase characters

• Core - Fixed notification emails being sent in English for users configured in French

• Core - Fixed repeated migration attempts after SQL migration and server restart

• PAM - Fixed "Nobody" account appearing when "Ignore system users" was enabled

• PAM - Fixed account discovery failure caused by circular security group membership

• PAM - Fixed Local Windows scan failure when credentials were linked

• PAM - Fixed SSH scan failure when sudo was configured with NOPASSWORD

## CONSOLE RELEASE NOTES ##

FIXES

• Core - Fixed basic installation failure when a generated password contained a single quote (')

@Marc-Andre Bouchard

Session recording PS sessions is cool.

I am already using the DVLS module, but was not aware of application-key option. It looks promising.

I am writing to suggest a change to the way 2FA is handled. It would be ideal if we could set a default value for users (2FA enabled), but to be able to disable it on a per-user basis. In my use case, everyone should have 2FA enabled (by default), but a service account, interacting with the application programmatically (e.g. with the Powershell module) cannot supply the second factor (and the PS module does not support the extra factor, anyway).