What’s New in Login Enterprise 6.7 | Workspace Weekly
July 8, 2026
This week’s Workspace Weekly highlights the Login Enterprise 6.7 release. For the complete list of new features, enhancements, improvements, and fixes, check out the official release notes.
Login Enterprise 6.7 helps teams improve Continuous Test reporting, troubleshoot workloads with less friction, simplify Windows 365 connector management, and strengthen operational control across API access, SSO, and Launchers.
This release introduces Continuous Test PDF reports, Application Performance details for Continuous Tests, UI Inspector Preview, Recorder enhancements, Windows 365 connector script management from the UI, role-scoped Public API tokens, AD FS support for OpenID Connect SSO, and new Launcher restart options.
Continuous Test PDF Reports and Application Performance Details
Continuous Testing is most valuable when teams can quickly understand what changed, determine whether the user experience remained within acceptable limits, and identify what requires follow-up.
Login Enterprise 6.7 makes Continuous Test results easier to review and share. You can now generate a PDF report for an individual Continuous Test, giving teams a more effective way to summarize results for application owners, infrastructure teams, change review boards, or other stakeholders who don’t work in Login Enterprise every day.
Imagine you are validating a monthly image update. The test ran, but a few application measurements or login-related metrics require closer review. Instead of sending screenshots or asking someone to navigate the results page, you can generate a focused report that clearly summarizes the outcome of that test.
Login Enterprise 6.7 also adds Application Performance details to Continuous Test results, giving teams a clearer view of application-level success rates, failures, and above-threshold measurements for the applications included in each Continuous Test.
That’s because Continuous Testing isn’t just about whether a session is launched; it’s also about whether the applications within that session continue to perform the way users expect. If an application begins taking longer to respond after a change, the results experience helps you identify that pattern more quickly.
Additional enhancements to the Continuous Test results experience in 6.7 further reduce friction during review. Current test configuration details are now available directly from the results page, threshold values are easier to identify in chart legends, and Launcher names appear in raw-data chart tooltips where applicable.
For more information, refer to: Viewing Continuous Testing Results | Generating a Test PDF Report and Application Performance.
Figure 1: Reviewing Continuous Test results and generating a PDF report in Login Enterprise 6.7
Easier Workload Maintenance with UI Inspector and Recorder Enhancements
Workloads rarely stay perfect forever. Applications change, UI elements move, buttons get renamed, fields behave differently, and recorded steps occasionally need attention.
Login Enterprise 6.7 introduces several enhancements that help teams build and maintain workloads with less guesswork.
UI Inspector is now available in preview. It lets you inspect UI elements in Windows applications and generate WinApp code snippets based on Script Recorder methods and logic. This is especially useful when a workload can no longer reliably locate a button, pane, field, or other control.
Imagine a workload has been running successfully for weeks. After an application update, the test begins failing because a UI element changed. Instead of rebuilding the workload from scratch, you can inspect the target element, review its element hierarchy and properties, test the detection method, and copy the generated code snippet directly back into the script.
This turns workload repair into a smaller, more focused task.
WinApp Recorder also introduces new options for fine-tuning how UI elements are located. Additional parameters for information-based element detection give teams greater flexibility when an element requires a more specific or more resilient locator.
The benefit isn’t simply having more settings—it’s having more control over how workloads are maintained. If a locator is too specific, it may break when a dynamic part of the UI changes. If it’s too generic, it may identify the wrong element. The new options help teams strike the right balance.
Recorder action settings have also been updated. When you open a recorded step, its settings are displayed immediately. Each step can use either global settings or custom settings, depending on whether you want it to follow the recording defaults or behave differently from the rest of the workload.
Action names are now editable as well. Updated action names appear as comments in the generated script, making longer workloads easier to read and maintain.
Web Recorder also receives several enhancements in 6.7. During web recordings, UI elements are highlighted on hover, making it easier to see exactly which element is being captured. Selector settings are available for recorded elements, selector testing can be performed while recording is paused, and Web Recorder now supports recording Google Workspace applications such as Gmail and Sheets.
For more information, refer to: UI Inspector, WinApp Recorder Settings, and Web Recorder.
Figure 2: Inspecting a UI element with UI Inspector Preview
Windows 365 Connector Script Management from the UI
Windows 365 validation depends on the Windows App, and the Windows App evolves over time. As the sign-in or connection experience changes, the connector script that automates that process may need to change as well.
Login Enterprise 6.7 simplifies Windows 365 connector management by adding script management directly to the UI. Instead of managing connector scripts exclusively through the Public API, administrators can now view available scripts, upload a custom script, download existing scripts, and delete custom scripts from the Windows 365 connector settings page.
This is an appliance-wide setting. When a custom script is uploaded, it is used for all Windows 365 connector tests running on that appliance. If the custom script is removed, Login Enterprise automatically reverts to the built-in default behavior.
This helps teams keep Windows 365 testing maintainable as the Windows App continues to evolve.
Imagine you’re validating Windows 365 Cloud PCs and a Windows App update changes part of the connection experience. Instead of tracking down scripts across Launcher machines or wondering which version is currently in use, administrators can manage the connector script centrally. Teams can rely on the built-in default behavior or upload a custom script when their environment requires it.
Login Enterprise 6.7 also improves Windows 365 connector script handling through the Public API, including support for working with scripts as .cs files.
For more information, refer to: Windows 365 Connector Script Management.
Figure 3: Managing Windows 365 connector scripts from Connector settings
Stronger Controls: RBAC API Tokens, AD FS SSO, and Launcher Restart
Login Enterprise 6.7 also introduces several enhancements for teams operating Login Enterprise at scale.
Public API tokens now support Role-Based Access Control (RBAC). Instead of relying solely on legacy token access levels, new system access tokens can be assigned to a role. API calls made with those tokens inherit the permissions granted by that role.
This gives teams more precise control over what each API token can do. For example, a token used for reporting doesn’t require the same permissions as one used for configuration or automation. Role-scoped tokens make it easier to align API access with the same permission model already used throughout Login Enterprise.
Login Enterprise 6.7 also adds support for AD FS as an OpenID Connect SSO provider. For organizations already using AD FS within their identity environment, this provides another way to align Login Enterprise authentication with existing SSO practices. Authentication is handled by the identity provider, while Login Enterprise continues to use LDAP for authorization and role assignment.
Launcher operations have also been streamlined. Administrators can now restart either the Launcher application or the Launcher machine directly from the Login Enterprise UI, reducing the manual effort required during troubleshooting and routine maintenance.
For larger deployments, these operational improvements can have a meaningful impact. Teams often manage Launchers across multiple locations, test types, or environments. Being able to restart a Launcher directly from Login Enterprise reduces the need to remote into individual machines simply to perform routine recovery or maintenance tasks.
For more information, refer to: Role-Based Access Control (RBAC) | Endpoints for Access Management, System Access Tokens, Single Sign-On (SSO), Configuring OpenID Connect (OIDC), and Restarting the Launcher.
Figure 4: Assigning a role to a Public API token
Figure 5: Restarting a Launcher from the Login Enterprise UI
Additional Improvements in Login Enterprise 6.7
Login Enterprise 6.7 also includes a variety of smaller enhancements that make day-to-day administration and testing more efficient.
Load Test and Application Test events can now be filtered by occurrence time. The Test Name filter has also been removed from results pages where the Test Run filter already provides the same functionality, helping simplify the filtering experience.
The Script Recorder experience includes improvements to dark mode when Script Editor is using the dark theme. X-Ray now exposes separate ControlType and Framework fields, making it easier to generate more accurate code snippets.
Launcher update API responses also provide clearer error messages in blocked scenarios, such as when active sessions are present or a Launcher type isn’t supported. In addition, active Launcher sessions can now be retrieved and aborted through the Public API.
The release also includes fixes across Public API behavior, LDAP authentication, Script Editor behavior, Windows 365 script ordering, Application and Load Test result pagination, database migration, Docker compatibility, and script execution.
For more information, refer to the official release notes.
Ready to Upgrade to Login Enterprise 6.7?
Upgrade your appliance and launchers, then use the documentation above to start applying these improvements to your testing, reporting, workload maintenance, Windows 365 validation, and operational workflows.
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.
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
