---
title: Litmus Edge Manager 2.31.9
slug: edgemanager-2-31-x/litmus-edge-manager-2319
createdAt: 2026-11-06T11:49:28.921Z
---

**Release date:** November 6, 2026

Review the current list of [Limitations](docId\:MRg6GMxJ4s8e56y0bNGXM).

## Enhancements and improvements

**Remote access:**

- Improved the reliability of Remote Tunnel connections to edge devices on restricted networks, such as Google Kubernetes Engine (GKE) Autopilot clusters.

**Marketplace: catalogs and applications:**

- Litmus Edge Manager (LEM) now enforces authentication on Marketplace Catalog GET API requests by default. You do not need to take any action after upgrading.

## Resolved issues

**Company:**

- Fixed an issue where single sign-on (SSO) users who received the Admin role through an identity provider group, such as an Azure Entra ID group, could not create a company.

**Edge devices:**

- Fixed an issue where a user with read-only permissions could change the API token in *Edge Devices > Manage > API*.
- Fixed an issue where the *Downloads* tab under *Edge Devices* showed an error message when it opened and did not sort the list by version. Clicking the **Version** column header now sorts the list.
- Fixed an issue where DeviceHub device statuses stopped appearing when the edge device metrics sync interval was set to `24` hours.

**Kubernetes deployments:**

- Fixed an issue where edge device activation failed on a fresh install with the error `project is not linked to the WireGuard subnet`.

**Remote access:**

- Fixed an issue where downloading the edge-zerotouch and opensource-licenses files from the Litmus Edge (LE) Remote UI through the LEM Remote Tunnel failed with `404 Not Found`. Direct access to the device was not affected. This fix requires LE 4.4.0 or later.

**Software update:**

- Fixed an issue where a user with read-only permissions could create a software update task for edge devices.
- Fixed an issue where a scheduled LE software update started immediately after a LEM upgrade instead of at its planned start time. Devices could reboot outside the planned maintenance window.

**Marketplace: catalogs and applications**

- Fixed an issue where adding an Azure Container Registry provider in the Marketplace failed with `Failed to add repository details`, even when all Azure details were correct.
- Fixed an issue where cloning an application version with a space in the new name failed without showing an error.
- Fixed an issue where a user with read-only permissions could launch, stop, delete, or update applications on edge devices.

**Admin Console: events**

- Fixed an issue where activation codes appeared in full in *Device Lifecycle* audit events. Activation codes are now masked, as they already were in *License* audit events.

**Admin Console: settings**

- Fixed an issue where a user previously created with the same username could not sign in with Azure Entra ID. Role assignment failed with `Username already exists and it is inactive`.
- Fixed an issue where the user details API reported a user with a directly assigned admin role as non-admin.

**Platform and security:**

- Fixed an issue where a fresh install or an upgrade could stall indefinitely because the LEM configuration service stopped responding during startup. The UI showed `The application is initializing` and the Admin Console was unreachable until the service was restarted manually.
- Fixed an issue on heavily loaded hosts where built-in health checks restarted LEM services before they finished starting, so the services never came up..
- Fixed an issue where an interrupted Vault backup prevented the Vault secrets service from starting after the next reboot.
- Fixed an issue where credentials sent in an incorrectly formatted `Authorization` header could appear in API responses and logs.
- Fixed security vulnerability CVE-2026-8763 in the Keycloak component.