What’s new in Kasm 1.18.0

Highlights

Features

  • Usability Enhancements

    • When deleting OpenID or SAML configs we now make it clear that this will delete any users associated with the config and include an indication of how many users will be affected. In addition you can now edit an OpenID or SAML config to see the list of users associated with the config.

  • Infrastructure Support Enhancements

    • Improved performance of orphan server cleanup on autoscale pools that have a large number of servers.

  • Kasm Image Enhancements

  • Kasm Desktop Service

    • TBD

  • Licensing Enhancements

Bugfixes

  • Fixed the bug where the error message is unreadable if a session times out on launch when it redirects to the dashboard cutting off the error message.

  • Fixed the bug causing the db healthcheck to log an error message

  • Fixed a regression bug when searching for users inside a group only the first page of results was searched.

  • Fixed a bug that prevented the db container from using the rolling tag when specified during installation or upgrade

  • Enabled manager and agent tornado log streams to be sent to centralized Kasm logs

  • Fix rare case where RDP HTTPS gateway can flood the Kasm Manager with logs.

  • Fixed bug where users could not connect to an AutoScaled Windows Server that was using the Kasm Desktop Service with the max simultaneous sessions per server set to 1

  • Added component IDs and endpoint to JWT authentication / authorization failures, when available. Appears as additional info in the expanded log record for the failure

  • Fixed issue where Kasm Manager could get stuck in “missing” state.