Login Enterprise 6.9 Login Enterprise 6.8 Login Enterprise 6.7 Login Enterprise 6.6 Login Enterprise 6.5 Login Enterprise 6.4 Login Enterprise 6.3 Login Enterprise 6.2 Login Enterprise 6.1 Login Enterprise 6.0
Auto Light Dark
Auto Light Dark
Login Enterprise 6.9 Login Enterprise 6.8 Login Enterprise 6.7 Login Enterprise 6.6 Login Enterprise 6.5 Login Enterprise 6.4 Login Enterprise 6.3 Login Enterprise 6.2 Login Enterprise 6.1 Login Enterprise 6.0

What's New in 6.7

  • When upgrading to Login Enterprise v6.7 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 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

  • You must now sign in using the full User Principal Name (UPN) configured in Active Directory, e.g., outside-name@outside-domain.com. Support for pre-Windows 2000 usernames and related workarounds has been discontinued. For details, see Login Format

Features

Changes/Improvements

  • A Refresh button is available for Continuous Test results when the selected time span has an end date in the future

  • The current configuration details for Tests are available on the Continuous Test results page

  • Disabled Tests are filtered out on the Continuous Test overview page

  • The threshold value is displayed in the chart legend of the Continuous Test results

  • Continuous Test scheduling is configured in a dedicated section on the Test configuration page

  • The Launcher name is shown in the chart tooltip for Continuous Test results when chart aggregation is set to “None” (raw data)

  • The Test name filter has been removed from the Load and Application Test result pages, as the Test run filter already provides the same filtering capability

  • Load and Application Test events can be filtered by occurrence time

  • Script Recorder's findByInformation method supports additional parameters (framework ID, value Pattern, and text Pattern) to enable more flexible and robust script creation

  • Global settings for each Recorder step are shown immediately when a step is opened, and can be overridden per step by selecting the Custom settings option

  • Action names in the Recorder are editable to provide clearer descriptions. Updated names appear as comments in the generated script

  • Script Recorder supports dark mode when Script Editor is set to the dark theme

  • During web recordings, the Recorder highlights UI elements on hover to indicate which elements are captured more clearly

  • Selector settings are now available for elements recorded by the Web Recorder. Selector testing is available when the recording is paused

  • X-Ray provides separate fields for ControlType and Framework (previously combined into Class fields), enabling more accurate code snippets

  • Application credentials are available from the applications object in the Web Recorder/Playwright script base

  • The Public API endpoint for Launcher updates returns descriptive error messages when the Launcher update cannot be performed due to active sessions

  • The Public API endpoint for Launcher updates returns descriptive error messages when a Launcher update cannot be performed because it’s a Linux Launcher

  • Active sessions can be retrieved and aborted via the Public API

  • Windows 365 connector scripts can be downloaded from and uploaded to the API as .cs files.

Bug Fixes

  • Updating an existing Test through the v7 API endpoint disables VSIMax, even when VSIMax was previously enabled in the UI

  • LDAP login with an alternate UPN suffix uses the UPN domain as the LDAP target instead of the configured domain controller

  • The “Automatically save debug output” of the Script Editor is always enabled, regardless of the setting

  • The ordering of Windows 365 scripts is incorrect, resulting in the wrong script being used when the version of the WinApp in use doesn’t match the script version

  • Using a wildcard in the Launcher Group filter works with numbers and/or special characters, but doesn't work with alphabetical characters

  • Some UI elements of the Create a New Application pop-up in Script Editor dark mode are unreadable

  • Selecting one or more results on the Application Testing (or Load Testing) results page and then navigating to another page via pagination triggers repeated TypeError: “Cannot read properties of undefined (reading ‘id’) errors in the browser console”

  • When configuring a Test using the RDS connector with a space in the RDS Broker / RDP Host field, Login Enterprise allows the space but fails to launch the resulting .RDP file

  • When upgrading Login Enterprise to the latest version, the Database migration process fails in case there are more than 2100 Application scripts on the appliance

  • Portainer doesn't work with Docker v29

  • Scripts that use the mainWindowClass parameter with a wildcard in the START() command fail to run

  • The Abort function doesn't abort the script when used in a script without a START() command