Devolutions ForumDevolutions Forum

VERSION 2022.1.12.0 (April 04th 2022)

VERSION 2022.1.12.0 (April 04th 2022)

avatar
Richard Boisvert

Server


Improvements

  • Core - Give more information to user when they can't be logged in
  • Core - Logs can be cleaned up with a timeframe
  • Core - Office365 authentication supports automatic user creation from a specific group
  • Core - Removed some exceptions sent to administrator that were not critical
  • Core - Support multiple vaults export


Fixes

  • Core - Fixed an issue if a vault template has been created
  • Core - Fixed an issue where DWL can't find the matching sub-connections
  • Core - Fixed issues in the login process
  • PAM - Fixed an issue where importing from a scan didn't work the first time
  • PAM - Fixed an issue where searching a PAM account changed the priviledged account folder
  • PAM - Fixed an issue with SSH scan
  • Web - Several UI fixes


Console


Improvements

  • Added the update release type in the instance summary


Fixes

  • Fixed an issue where Devolutions Gateway service was set to manual start after an update
  • Fixed an issue where gateway side by side didn't work after Devolutions Server update
  • Fixed several UI issues
  • Validate the minimum Devolutions Console version needed before updating Devolutions Server


Richard Boisvert

All Comments (4)

avatar
justpaul

Thanks for the update, Richard. Would you please provide additional details for:

  • Core - Fixed issues in the login process


Thanks,
Paul

avatar
François Dubois

Hi Paul,

We fixed two important things around the login process. First, we had issue with DVLS installation with a server doing the ssl offloading in front of DVLS. It could be a load balancer/reverse proxy, but those cases were not supported. Now, we support those setups, but it is important to know for those setups that only one "Access URI" is possible. When you configure your DVLS instance in the console, there is a field Access URI and a list can be provided. For setup with ssl offloading, only one is supported for now.

The second thing that has been fixed is an issue for some installation. DVLS was calling itself in previous version during the login process. In some installation, that call was not possible and the full login process was aborted. So we fixed that issue as well.

Did you ask the question because you had an issue with the login process ? If it is the case, plese let us know what is your issue, it will be a pleasure to help you.

Best regards,

François Dubois

avatar
sebastianmair

Hi, after upgrading to 2022.1.12.0 windows authentication is not working anymore,any ideas? it says only "connection failed".

when i use %username% the browser pops up and i cann login with the weblogin.

this is very annoying....

kind regards,
sebastian

avatar
Erica Poirier

Hello,

Thank you for reporting this problem.

What RDM version are you using?

Do you have any relevant error messages in the DVLS logs or in Reports - Login attempt?

Could you please enable the Log4net utility and send us the DPS_Main.log file at service@devolutions.net? Please add a reference to this forum's thread.
https://kb.devolutions.net/kb_dvls_enabling_log4net_log.html

Best regards,

Érica Poirier