Updating the Appliance from v5 to v6

Overview

This section outlines the update process for migrating from Login Enterprise v5 (5.0 to 5.14) to any v6 release.

• Login Enterprise v5.8 and older can't be updated directly to v6. However, Login Enterprise v5.9.8 through v5.14.7 can be updated directly to v6 if you initially installed one of those versions, or if you have performed the system update to Debian Linux 12 as part of the upgrade to one of those versions.

• Before upgrading to v6, you must upgrade Debian to v12. This upgrade is available for Login Enterprise v5.9 and higher. For details, see Updating Debian on the Appliance.

• Once you are on Debian Linux 12, you can upgrade from Login Enterprise v5 to any v6 release.

1. Before updating, ensure you have a backup or snapshot of your Virtual Appliance. If you are using the optional SQL database for data storage, back it up as well.

2. Mount and attach the Login Enterprise v6 ISO to your existing Virtual Appliance via your virtualization management platform.

Upgrade Limitations

• Launchers from previous versions of Login Enterprise (before v6.0) are not compatible with Login Enterprise v6. Therefore, all Launchers must be upgraded when you upgrade to Login Enterprise v6. This only applies when upgrading from v5 to v6

• The upgrade to v6 will be blocked under the following circumstances:

  • If you're on v5.8 or lower

  • If you're on v5.9–5.14 but still using Debian 10

  • In these cases, you'll need to perform specific actions before upgrading:

    • For v5.8: You must update Linux before upgrading. To do this, perform an upgrade to v5.14 and select “Perform System Upgrade”

    • For v5.9 without Debian 12: You must update Linux before upgrading. Upgrade to v5.14 and select “Perform System Upgrade”. If you’re already on v5.14, perform the upgrade to v5.14 again with the “System Upgrade” option

• If you currently log in using an LDAP account with the format DOMAIN\USERNAME (UNC format), note that this is no longer supported in v6.0 and higher. You must use the format USERNAME@DOMAIN (UPN format) to log in

• Migration to v6 ensures that users assigned to the Admin or Read-Only LDAP groups can still log in after the upgrade. However, these migrated roles are not automatically assigned to Tests. As a result, users may not be able to see any Test data unless the appropriate roles are assigned to the Tests.

  • To resolve this, Login Enterprise provides API endpoints that allow administrators to bulk update Tests and Test Runs to assign or replace the roles. For details, see API Endpoints for Access Management.

  • You can also assign roles to a Test individually through the Login Enterprise UI in the Test Configuration.

  • In v6.1 and later, Tests are automatically assigned to the Built-In Admin role.

Steps to Update to v6

For detailed steps, see Online Update of Login Enterprise.

Steps after Upgrading

• All Login Enterprise Launchers connected to your Login Enterprise Virtual Appliance will need to be updated. For details, see Launcher Maintenance and Updates.

  • The Login Enterprise v6 Launcher needs to be downloaded from your Login Enterprise. For details, see Downloading and Installing the Launcher.

  • To update the Login Enterprise Launcher agent on each Launcher host, the Launcher installer/updater needs to be run on each by either:

    • Silent installation. For details, see Silent Installation.

    • Graphical Launcher installation, invoked by running the Launcher installer (double-clicking on it if in the Downloads folder, for example) and following the installation prompts in the installation interface.

• To verify that the new Launcher installations are successful, run the Launchers, and the Launcher agent UI will look like this, with the new version showing in the top window banner (Login Enterprise Launcher v6.0.4 in this example), and the bottom a green banner reading “Connection status: Connected.“

• If a Launcher hasn’t been updated yet, the bottom orange banner would read “Connection status: Idle (update the Launcher to the latest version)“.

Role-Based Access Control (RBAC)

Login Enterprise v6.0 introduces the first version of role-based access control (RBAC). Currently, RBAC is only supported with LDAP (Active Directory) authentication and requires LDAP users and groups for access management.

If you have LDAP set up, you can enable RBAC. Without LDAP integration, RBAC cannot function. To learn more about RBAC, use cases, permission dependencies, and more, see Role-Based Access Control (RBAC).