Known Issues - Post-release - Fixed with UMS 12.08.110

AD / LDAP integration

  • AD login could fail when an UPN suffix was used for an AD user and with that the logon with user@domain name was not possible.

Cloud IdP / SSO

  • UMS console login with hostname (without domain) no longer worked.

  • Allow FQDN with uppercases.

  • Integrate umsstarter into RMClient.exe (updating installer and protocol registration) to eliminate the separate JAR.

Console, common

  • UMS Console only installations could run into a login/connect error if they were never connected to the UMS server.

  • The use of a hostname to connect to the console was not possible.

Devices

  • Timeout issues while saving settings of a device.

Installer (Linux)

  • Installer could not register mimetype for console login when package desktop-file-utils was missing on some Linux Systems.

  • Linux installation took a very long time on some systems.

  • On Ubuntu 22.04 and 24.04 when UMS was installed as a non-root service, the error "Wrong password" was always shown.

Server, common

  • OS 11 devices could not download assigned CICs. (OS 11 devices connected via ICG and OS 12 devices were not affected)

UMS common

  • Null pointer exception when reading a configuration file.

WebDAV

  • In Distributed UMS or HA environments, the WebDAV file synchronization failed.

UMS Web App

Misc

  • Login to the UMS Web App failed if the UMS Server is not listening on the default port (8443)

  • Removed unused dependency org.apache.httcomponents.client5:httpclient5:5.4.2

  • Igel-rest-libs version 12.8.2 was removed from the build.

  • Several dialogs were wrongfully displayed in full width in Chromium-based browsers.

Users

  • When a user is reassigned to a different group while logged in, the UI did not consistently reflect the change.

Configuration

  • Additional timeout issues while saving settings of a device.

  • Permissions for a device-record were not properly calculated if the device was in bin on server-start and restored afterwards.

  • Not all received changes were correctly flushed into the index.