What’s new in Kasm 1.11.0
Features
Infrastructure Support Enhancements
Added OpenID Connect Authentication feature to allow Single SignOn with third party identity providers.
The Cloud Autoscaling feature is now informed by Staging Configs.
Updated Developer API with additional endpoints for managing Session Tokens.
Updated Developer API with additional endpoints for managing Shared Session Permissions.
Added Google Cloud (GCP) support to the Cloud Autoscaling feature.
Added Azure support to the Cloud Autoscaling feature.
Kasm JSON logs now include millisecond resolution on the asctime and timestamp fields
Using a new flag
forward_logs_to_manager
inagent.app.config.yaml
it is possible to disable the kasm agents from forwarding their logs to the kasm manager to be logged in the database. This helps to reduce disk space consumption on large deployments where alternative log management (e.g. splunk or datadog) are in place.Added enhanced support for multiple SSO Group Mappings. Administrators can now add more, complex mappings including mapping all users from a particular SSO provider to the group.
Added Valid Until setting to Casting Configs allowing the administrator to expire links after a set time.
Added Enforce Client Settings to Casting Configs allowing the administrator to force settings like Allow Downloads to an specific Casting session - overriding a users Group settings.
Added GPU Support for Graphics Acceleration.
Added more GPU statistics to Agent View.
Changed GPU resource allocation to match CPU core allocation. More details in CPU / Memory / GPU Override.
Added an option to the global settings that marks an agent as enabled automatically when it first checks in.
Kasm Image Enhancements
Updated Ubuntu based Kasm images to be built on Ubuntu Focal 20.04 LTS
GPU support for Ubuntu Focal core image and derivative images.
Added openSUSE Leap 15.x core and desktop images for x86_64/aarch64
Added Oracle Linux 8 core and desktop images for x86_64/aarch64
Expand aarch64 application images previously only built for x86_64: : - Added Java Development Desktop for aarch64
Added Sublime Text for aarch64
Added Telegram for aarch64
Added Tor Browser for aarch64
Added Doom for aarch64
Added LibreOffice for x86_64/aarch64
Added Thunderbird for x86_64/aarch64
Added Atom for x86_64
Added Audacity for x86_64/aarch64
Added Deluge for x86_64/aarch64
Added FileZilla for x86_64/aarch64
Added Inkscape for x86_64/aarch64
Added Pinta for x86_64/aarch64
Added qBittorrent for x86_64/aarch64
Kasm security Enhancements
Kasm api server no longer returns full stack traces when an API call exceptions. This limits information that can be gleaned by an attacker purposefully causing exceptions.
Credentials stored by Kasm for other services such as the image docker token, or the LDAP service account password are now encrypted when stored in the database.
Usability Enhancements
Added a dark theme option to the Kasm Workspaces UI.
Added a pointer lock feature to the session control panel that will lock the mouse cursor to the browser window. This can be helpful for some activities such as gaming.
Kasm Workspaces now supports Input Method Editor (IME) which allows for a user to input characters not represented on a standard QWERTY keyboard
Bugfixes
Fixed an issue where the Workspaces dashboard would exception if an image friendly name began with a number.
Fixed an issue where if a kasm service did not exit cleanly it could leave behind temporary files that could eventually consume all available harddrive space.
Fixed a logic error in named user licensing that caused there to be one less user slot available than the license specified.
Fixed PulseAudio not starting properly when a persistent home directory is mounted over NFS.
Fixed Brave Browser profiles not loading on latest development images.
Fixed Web Filter not working when Workspaces was deployed on a non-standard port.
Removed Slack image from catalog and desktop images due to lack of functionality in a Docker container.
It’s possible for KasmVNC to get in a state where it believes that the MacOS command key is stuck in the down(pressed) position. Users can now refresh their browser tab with the Kasm session and it will reset all keys to the up position.