Overview
Due to increasing demands for ease of management and compliance with security protocols, Group Policies are frequently employed to modify default browser paths. This practice previously led to unnecessary application execution errors within Login Enterprise. Starting from Login Enterprise 5.5, non-default profile paths for browsers such as Edge and Chrome are fully supported for Browser-based workflows.
Configuring browser profile path
To configure a non-default path for the Login Enterprise to use when running EdgeChromium browser-based workflows, follow these steps.
Adding an Application
When creating a new application workflow within the virtual appliance management console, you will encounter a configuration menu where you can specify the Application name. You can also set which browser to use and define the URL to launch once started.
Additionally, the configuration menu includes a Browser Profile option. This allows you to specify non-default profile paths.
Default vs. сustom browser profile paths
- Default browser paths, such as those for Chromium (Microsoft Edge and Google Chrome) and Firefox, are automatically used if browsers were installed using standard settings. These paths store user-specific data like cookies and configurations.
- Сustom browser paths are specified by users who require tailored configurations, often for centralized management or compliance reasons. Custom paths ensure specific user settings are applied during testing, maintaining accuracy and adherence to organizational policies.
Updating an existing Application
This section covers steps to modify existing application workflows to utilize non-default browser profile paths.
Using a 'magic comment'
To specify the browser and the URL that the browser should launch within our browser-based workflows, use 'magic comments' located at the top of the workflow script. These comments are typically found on lines 1 and 2. You can also add a third comment on line 3 to specify a non-default profile path, as illustrated below:
// BROWSER:EdgeChromium
// URL:https://euc.loginvsi.com/customer-portal/knowledge-worker-2023
// PROFILE_LOCATION:%LOCALAPPDATA%\Google\Chrome\User Data\Default\
To learn more about the 'magic comments', see Using // TARGET: comments for CLI automation.
Updating Application configuration
After making changes to your existing workflows, you should overwrite the current workflow defined for the respective application.
To overwrite an existing script, click the pencil icon, which opens a configuration window. This window simplifies the display of any differences between the current and new workflow scripts, allowing you to review changes before overwriting your existing workflow.
If you have updated your script to include the new 'magic comment,' you will see the Browser profile section specify your non-default location. Make sure to select 'New parameters' to overwrite existing settings.
Event logging
The issue arising from non-default profile paths is rooted in Selenium's requirement to locate and load a specific browser profile from its default location when initializing a browser session. Consequently, an event in Login Enterprise indicates that it 'cannot create default profile directory'.
To learn more about Event logging, see the Event logger.