Database upgrade required
If you are using RDM as the client, RDM 2022.3 is required for this DVLS version
NEW FEATURES
Core - Added a way to migrate users from an authentication mode to another (from Active Directory to Azure AD for exemple)
Core - Added permission set to assign permission easily on users
Core - Added support to Okta authentication
Core - Added support to SMTP modern authentication with Azure
Core - Implemented attachment and documentation support for sub connections
Gateway - Added Kerberos authentication via KDC Proxy
Gateway - Added new reports to display Devolutions Gateway permission
Gateway - Added permissions on Devolutions Gateway
Gateway - Sessions launched via Devolutions Gateway can now be killed
PAM - Added description field on PAM account
PAM - Added support for generic providers
Web - Added markdown WYSIWYG documentation editor
IMPROVEMENTS
BREAKING CHANGES Core - RDM User license must be set in the data source
BREAKING CHANGES Core - RDM users need one license assigned for each user account
Core - Added a button to refresh favorites
Core - Added a way to select the main account type to bypass the authentication type on login
Core - Added an option to select Azure behavior on login
Core - Added one button in login page for each Active Directory configured
Core - Added options to select Azure behavior on login
Core - Added support for multiple emails in email configuration
Core - Button label can now be configured in login page
Core - Connection icon can now be customized
Core - Improved RDM connection stability with Devolutions Server
Core - Improved security dashboard UI
Core - Removed the option "Current Windows session" as credentials for AD configuration
Core - Renamed 'Custom User' by 'Devolutions Server User'
Gateway - Added a filter in the Devolutions Gateway list
PAM - Added log messages if PAM password propagation failed
PAM - Added possibility to include PAM vaults in search side bar
PAM - Changed the way PAM account are displayed: Removed tiles and display a tree
PAM - Improved PAM Heartbeat failed message to differenciate provider and account name
FIXES
Core - Fixed an issue where administrator received an exception about telemetry when internet was not available
Core - Fixed an issue where attachments were corrupted after download
Core - Fixed an issue where backup was failing with invalid path on Linux SQL Server
Core - Fixed an issue where folder structure was visible in DWL even if user didn't have access to the folder
Core - Fixed an issue where importing Azure AD accounts didn't fill the first and last name
Core - Fixed an issue where license capacity could be exceeded
Core - Fixed an issue where Okta groups were recognized as Devolutions Server groups
Core - Fixed an issue where Okta groups were viewed as Devolutions Server groups
Core - Fixed an issue where password set on an attachment was not shown correctly
Core - Fixed an issue where read only users could add attachments or documentation
Core - Fixed an issue where SMTP configuration was not migrated correctly
Core - Fixed an issue where success page was prompted after Windows Authentication
Core - Fixed an issue where user update could lost user group assignments
Core - Fixed an issue where username field could be missing in Emergency Login
Core - Fixed an issue where users avatar were missing
Core - Fixed an issue where Website entry could not be saved with a Password Management license
Core - Fixed an issue where wrong RDM version was loged in reports
Core - Fixed issue in My Account Settings where Dashlane Password and KeePass Server Password were not obfuscated
Core - Fixed issue where email could not be sent in some cases
Core - Removed sensitive information from public endpoint
PAM - Added log message if password propagation failed
PAM - Fixed an issue where PAM section was not available even with a license
Web - Several UI fixes
## CONSOLE RELEASE NOTES ##
IMPROVEMENTS
Add read right to IIS_IUSRS on encryption.config file
Minor update
Removed the Basic authentication and Digest authentication from the prerequisites
Set the Devolutions Gateway ID when Devolutions Gateway is installed side by side
FIXES
Fixed an issue where an error was raised for invalid signature with Devolutions Gateway when installed via CLI
Fixed an issue where Devolutions Gateway side by side installation button was grayed out
Fixed an issue where semicolon was not accepted in SQL Server password
Érica Poirier
Hi Erica,
maybe this is a wrong place for complaint/suggestion but this "If you are using RDM as the client, RDM 2022.3 is required for this DVLS version" is happening way too often.
Maybe you should implement ClickOnce app deployment, we cannot deploy all the clients via msi installation at the same time (especially if the new client should not connect to older data source).
Best regards,
Rok
Hi Rok,
Every communication channel is good to contact us for submitting suggestion, questions or raise issues. Next time for any feature request, you can post in these sections.
For RDM : https://forum.devolutions.net/forums/17/remote-desktop-manager--feature-request
Fro DVLS : https://forum.devolutions.net/forums/34/devolutions-server--feature-request
That being said, we recommend using the same major version for both the server and client application (first 2 numbers like 2022.3) for better compatibility as both applications are closely related. Here is the Version Schema Compatibility chart for RDM and DVLS.
For your suggestion about ClickOnce, I will inform our engineering team about it.
Best regards,
Érica Poirier
Hi Rok,
I want to add that RDM 2022.2 can connect on DVLS 2022.3 so it offers extra time to allow your team to properly deploy the newest RDM version. But to prevent having unwanted behaviours or issues, we recommend to match the client version with the server version as soon as possible.
Let us know if you have further questions about this.
Best regards,
Érica Poirier