What’s new in Kasm 1.13.0

Features

  • Infrastructure Support Enhancements

    • Added support for using databases with non standard name and user.

    • Updated installer with more verbose storage requirement information and allow users to bypass if needed.

  • Usability Enhancements

    • Added support for Fullscreen in a Kasm session.

    • Added support for installing Kasm as a PWA. User Guide / Admin Guide.

    • Moved Google Recaptcha Global Setting from the Cast to Auth category.

    • Server pools now select the oldest server available for a pool when connecting. This helps ensure servers in the pool are fully configured by the startup script before attempting to connect.

    • Added Workspace Registry to make it easier to install workspaces.

  • Infrastructure Support Enhancements

  • Kasm Image Enhancements

Bugfixes

  • Fixed a bug which prevented the use of the session_time_limit group setting.

  • When updating a Server Workspace, changes to the selected server would not apply when submitted.

  • Connecting to Server and Server Pool based workspace sessions would fail if credentials were not defined on the Server record.

  • kasm_api service now logs 404s as warnings instead of errors.

  • Phone number uses the correct phone field instead of the organisation field on the user profile.

  • Check for lsof during install and install if not found.

  • Properly parse user input and use correct manager token for Agent role install.

  • Updated Github OIDC integration to support mapping in the Github user’s email address.

  • Fixed issue with request_kasm and join_kasm developer APIs that prevented sessions from being created when the caller wished to create an anonymous user.

  • Fixed an issue during the 1.12 migration that prevented editing of Kasm agents.

  • Fixed incorrect endpoint path being used in multi-server deployments for manually logging with username/password into RDP servers