-
When upgrading to Login Enterprise v6.8 from a version older than 6.3, all existing API tokens will become invalid and must be manually recreated. You can do this in the Login Enterprise UI. For steps, see Adding a System Access Token
-
The new UI and Public API Launcher upgrade feature introduced in v6.6 is only compatible with Windows-based Launchers already running v6.6 or higher. Launchers on older versions must be updated manually one final time
-
For other upgrade limitations and detailed steps on upgrading the Appliance from v5 to v6, see Upgrading the Appliance from v5 to v6
Features
Changes/Improvements
-
The Login Enterprise UI includes accessibility improvements that address the most common high-severity WCAG 2.1 issues
-
The built-in RDP connector supports the new Microsoft security prompts introduced in April 2026
-
The Launcher can interact with higher-privilege Windows prompts without itself running as administrator. To use this feature, the Launcher must be installed in a secure location, such as the Program Files directory
-
The Appliance supports ECC (Elliptic Curve Cryptography) certificate and its EC private key for front-end TLS
-
Launcher restarts and updates can be scheduled through the Public API
-
Custom Connector SDK includes an email field
-
The Engine “waiting“ dialog can be moved, allowing underlying screens to remain visible
-
The Engine toolbar provides more space to display the full Environment and Account names
-
Script Recorder's update name option is always visible instead of appearing only on hover
-
UI Inspector action list has been extended with Type to control, Focus control, Focus window, Find control, Find Window, and DumpHierarchy
-
Login failure and application failure notification emails include the failure timestamp, Launcher name, Account name, and Target Host
-
Login performance, Application performance, and Latency notification emails include the Target Host
-
The Continuous Test overview page displays the current schedule type: Always on, Daily, or Weekly
-
The list of default Windows 365 scripts has a label identifying the latest version
Bug Fixes
-
Performance-above-threshold metrics on the Continuous Test overview page include disabled thresholds
-
Upgrades to Login Enterprise 6.5 or later can take a long time for large databases because of a non-optimal database query
-
Testing against a Citrix-published desktop with Seamless Mode enabled results in "The launcher did not respond to a session request in a timely fashion" errors. This affects both Storefront and NetScaler connectors
-
The Windows 365 connector fails when a temporary window or pop-up appears and disappears during script execution
-
Recorded double-click actions are labeled as left clicks in the generated comment and action name
-
Application scripts fail to find the application window when the mainWindowClass in the StartApplication method contains a colon
-
The Save and run Test option in the UI saves changes to the Test but does not trigger a run of the Test