Workload Maintenance and Platform Controls in Login Enterprise 6.7 | Workspace Weekly
July 29, 2026
Login Enterprise workloads and supporting platform controls rarely stay static.
Applications change. UI elements move. Authentication requirements evolve. API access needs to be scoped more carefully. Launchers occasionally require recovery or maintenance.
This week’s Workspace Weekly looks at several improvements in Login Enterprise 6.7 that help teams maintain workloads with less guesswork and manage the platform with more direct control.
The release adds UI Inspector Preview, improvements to WinApp Recorder and Web Recorder, role-scoped Public API tokens, AD FS support for OpenID Connect SSO, and new Launcher restart options.
For the complete list of features, enhancements, improvements, and fixes in Login Enterprise 6.7, check out the official release notes.
Repair Windows Workloads with UI Inspector Preview
Windows application workloads can run reliably for weeks or months and then begin failing after an application update.
A button may be renamed. A control may move within the element hierarchy. A field may expose different properties. A locator that once worked may become too specific or may no longer identify the intended element.
Login Enterprise 6.7 introduces UI Inspector Preview to make this kind of workload repair more focused.
UI Inspector lets you select a control in a Windows application and inspect its element hierarchy and available properties. You can choose how the control should be detected, test the detection logic, and generate WinApp code based on Script Recorder methods.
Instead of rebuilding a workload or manually guessing which locator needs to change, teams can narrow the problem to the affected control and work directly with the information exposed by the application.
Imagine a workload begins failing after an Office update because it can no longer find a ribbon control. UI Inspector can be used to inspect the control; review its class name, automation ID, name, framework, and other properties; and test a new detection method before copying the generated code back into the script.
This turns a broad workload failure into a smaller, more focused repair task.
For more information, refer to: UI Inspector.
Figure 1: Inspecting a Windows application control and generating WinApp code with UI Inspector Preview
Fine-Tune Recorded Actions with WinApp and Web Recorder Improvements
Login Enterprise 6.7 also adds several Recorder improvements that help teams create and maintain more readable and resilient workloads.
WinApp Recorder provides additional options for information-based element detection, giving teams more control over how UI elements are located when the default locator is too specific, too broad, or sensitive to dynamic application changes.
When a recorded action is selected, its settings are now shown immediately. Each action can use either the global recording settings or its own custom settings, depending on whether the step should behave like the rest of the workload or requires more specific handling.
Action names can also be edited. These names appear as comments in the generated script, making longer workloads easier to understand and maintain.
Web Recorder receives related improvements in 6.7. UI elements are highlighted during recording, selector settings can be reviewed and tested, and Google Workspace applications such as Gmail and Sheets can now be recorded.
These changes do not remove the need to understand how an application behaves, but they give workload authors more control when an application requires a more deliberate approach to locator or action configuration.
For more information, refer to WinApp Recorder Settings and Web Recorder.
See It in Action: Interactive Login Enterprise 6.7 Demo
The walkthrough below shows how UI Inspector can be used to inspect, test, and generate code for a Windows application control. It also covers role-scoped API tokens, AD FS configuration, and Launcher restart controls in Login Enterprise 6.7.
The workload-maintenance features help teams repair and refine scripts. The remaining improvements in this post focus on controlling access, authentication, and Launcher operations.
Scope Public API Tokens with Role-Based Access Control (RBAC)
Public API access often serves different purposes.
A reporting integration may only need permission to retrieve results. An automation workflow may need to create or modify configurations. Administrative integration may require broader access.
Login Enterprise 6.7 adds Role-Based Access Control support for new system access tokens.
Instead of assigning one of the older static access levels, administrators can assign a token to an RBAC role. API calls made with that token use the permissions granted to the selected role.
Figure 2: Assigning an RBAC role and lifetime to a new system access token
This makes it easier to align API access with the same role model used elsewhere in Login Enterprise.
For example, a token used by a reporting system does not need the same permissions as one used to configure tests or manage the environment. Role-scoped tokens help teams grant access based on the needs of each integration rather than providing broader access than required.
Existing legacy tokens remain available, but new system access tokens can use the more precise RBAC model introduced in 6.7.
For more information, refer to Role-Based Access Control, System Access Tokens, and Using the Public API.
Connect AD FS Single Sign-On Through OpenID Connect
Organizations often want Login Enterprise authentication to align with the same identity practices used across the rest of their environment.
Login Enterprise 6.7 adds AD FS as a supported OpenID Connect identity provider.
Administrators can configure the AD FS issuer URL, client ID, client secret, and redirect URL from the SSO Configuration page. SSO can then be enabled and, when appropriate, enforced for users.
Figure 3: Configuring AD FS as an OpenID Connect provider in Login Enterprise
AD FS handles authentication, while Login Enterprise continues to use LDAP and assigned roles for authorization.
This gives organizations already using AD FS another way to bring Login Enterprise sign-in into their existing identity environment without changing how platform permissions are assigned.
For more information, refer to Single Sign-On and Configuring OpenID Connect.
Restart Launchers Remotely from the UI or Public API
Launcher recovery and maintenance can become repetitive in environments with multiple Launcher machines, locations, or test types.
Login Enterprise 6.7 lets administrators restart either the Launcher application or the Launcher machine directly from the Login Enterprise UI.
Figure 4: Restarting a Launcher application or machine from the Login Enterprise UI
This can reduce the need to remote into an individual Launcher simply to perform a routine restart.
Restarting the Launcher application can help when the application itself needs to be refreshed. Restarting the machine provides a broader recovery option when the operating system or Launcher host requires attention.
Teams that automate Launcher operations can also restart the Launcher application or machine through the Public API.
The following minimal PowerShell example restarts one Launcher. Set $restartType to application to restart the Launcher application or machine to restart the Launcher host.
$baseUrl = "https://your-login-enterprise-appliance"
$token = "<your-system-access-token>"
$launcher = "<your-launcher-name>"
$restartType = "application" # application or machine
$headers = @{ Authorization = "Bearer $token"; Accept = "application/json" }
$body = @{ launcherNames = @($launcher); restartType = $restartType } | ConvertTo-Json
Invoke-RestMethod -Method Put -Uri "$baseUrl/publicApi/v8-preview/launchers/restart" -Headers $headers -ContentType "application/json" -Body $bodyExample: Restarting a Launcher application or machine through the Public API
For more information, refer to Restarting the Launcher.
Login Enterprise 6.7 at a Glance: Maintain Workloads and Control the Platform
Login Enterprise 6.7 brings together several improvements that address different parts of day-to-day platform ownership.
UI Inspector and Recorder enhancements help teams repair and refine workloads when applications change.
Role-scoped API tokens make it easier to match integration access to the required permissions.
AD FS support provides another option for aligning Login Enterprise authentication with an existing identity environment.
Launcher restart controls reduce the manual effort involved in routine recovery and maintenance.
Together, these improvements make workloads easier to maintain and give administrators more direct control over how Login Enterprise is accessed and operated.
Ready to Get Started with Login Enterprise 6.7?
Upgrade your appliance and launchers, then use the documentation above to start applying these improvements to workload maintenance, API access, authentication, and Launcher operations.
To set up a new appliance or update an existing one, go to Downloads. If your Appliance already exists and is internet-connected, follow Updating Login Enterprise. Don’t forget to take a snapshot first.
If you are not yet a Login Enterprise customer and are interested in becoming one, request a custom walkthrough with our team of EUC experts.
As always, we appreciate your feedback and use your insights to make Login Enterprise better for you.
Stay tuned for more Workspace Weeklies and join our Slack channel #workspace-weekly to share field stories, tips, and interesting finds.
To see all Workspace Weekly posts, visit the Workspace Weekly hub.
Login EnterpriseWorkspace Weekly
