Version 2024.3.2.0 (September 23, 2024)

Resolved

Version 2024.3.2.0 (September 23, 2024)

avatar

If you use a client (RDM, PowerShell, etc.), version 2024.3 is required for this DVLS version

See the What’s New in Devolutions Server 2024.3 blog article about the new features!

NEW FEATURES

  • Core - Added a feature to restrict license auto assignation to specific user groups
  • Core - Allow users to specify permissions requested in temporary access request
  • Core - Web sessions can now be recorded in the browser
  • PAM - Added automatic check-in for PAM accounts
  • PAM - The Active Directory (AD) provider can now manage local accounts on domain machines


BREAKING CHANGES

  • BREAKING CHANGE Core - The legacy recording server is no longer supported


IMPROVEMENTS

  • Core - Added an action available on an entry to easily share that entry
  • Core - Added duplicate for documents stored in database
  • Core - Added expiration time configuration when sending via Devolutions Send
  • Core - Added new 'high-priority' feature in messaging
  • Core - Devo-Send can now be used with Devolutions Server Free edition
  • Core - Export entry tags in 'Entry security analyzer' report
  • Core - Groups can be synchronized with their identity provider
  • Core - Improved offboarding of users by allowing conversion of user vault to a shared vault and unassigning licenses when deleting a user
  • Core - It is now possible to regenerate an application's secret
  • Core - Kestrel installation runs scheduler tasks
  • Core - The Entry Security Analyzer report no longer loads all vaults by default, improving initial load time
  • Core - User groups not found during provider group synchronization now appear as a warning log instead of an error
  • Core - Users and groups can be configured to be synchronized on a regular basis
  • PAM - Improved AnyIdentity provider to be able to use Devolutions Gateway
  • PAM - Just-In-Time (JIT) requested groups now appear in the logs when a request is made during checkout
  • PAM - Support for additional entry types added to PAM usage policy


FIXES

  • Core - Fixed a performance issue with Active Directory (AD) console
  • Core - Fixed an issue where a document stored in the database could not be duplicated
  • Core - Fixed an issue where a user with a password ending in a space was not functional
  • Core - Fixed an issue where quick connect didn't create logs
  • Core - Fixed an issue with viewing template groups correctly
  • Gateway - Vault's custom variables are now resolved for entries configured with a Devolutions Gateway
  • PAM - Allow application identities to utilize PAM through PowerShell module
  • PAM - Fixed an issue where a user could approve their own check-out even if they didn't have the rights
  • PAM - Fixed an issue where the "Run As" password was erased when editing the provider
  • Web - Several UI fixes


## CONSOLE RELEASE NOTES ##

FIXES

  • Fixed an issue where the instance password was not validated to access instance details


Érica Poirier

All Comments (5)

avatar

Apparently the inability to view Secure Notes was fixed in this version but it's not in the release notes - can you please confirm?

avatar

So 2024.2.x should be "Stable release" now?

avatar

Hello @sjames,

I'm not sure exactly what issue you are talking about. We made a fix a few weeks ago in RDM, is it what you are talking about ?


Hello @nicpa,
Yes, our 2024.2 should be our stable version soon. We plan one more release before the end of the week, probably tomorrow, to fix a few issues and we will flag that version stable.

Don't hesitate if you have other questions,
Best regards,

François Dubois

774e8ef9-f9a4-43d9-83b7-277ad8382486.png

avatar

Hello,

Regarding this improvement "Core - Devo-Send can now be used with Devolutions Server Free edition", error is experienced when Send by email or Create shareable link:





In Devolutions Server Console the log indicates an exception towards DevolutionsSendMessageService, is configuration required? I appreciate your support

6a39da67-f6cb-4415-be2d-cd1817563eb6.png

f28dd347-f434-419a-9328-354c21110789.png

4ff60948-a0a6-48fd-bcf6-1c6e59c71449.png

avatar

Hi erodriguezc77,

We are aware of this issue, as it affects the entire Devo Send feature. We have corrected the problem, and the fix will be available in the upcoming version, which will be released shortly.
Thank you.

Marc-Andre Bouchard