A proxy server is a server that acts as an intermediary between the user's computer and the Internet. It allows client computers to make indirect network connections to other network services. Today, corporations often use proxy to implement Internet access control for security reasons like authentication for Internet connection, bandwidth control, online time control, web filter, content filter, etc. This allows them to control what goes out and comes in to their network and helps with data and information protection.

LEAPWORK has a dedicated Proxy settings section, under Settings, where users can define proxy as per their company requirements. The proxy settings are divided into three different sections ‘Web blocks’, ‘Controller’ and ‘Studio’ proxy.

If users face any issues while starting/running test, they must contact their network security/IT Support team to get information about proxy implementation within their organization and configure these in the LEAPWORK Proxy settings.

LEAPWORK Proxy Settings

Let’s walk through all Proxy settings one by one.


Web Blocks

LEAPWORK Web Blocks are using Selenium as the backend engine to drive the web application-based tests. Selenium requires proxy information to run web applications in a secure network where proxy implementation is mandatory. 

LEAPWORK Web Blocks proxy is created to make sure that all web blocks use the proxy configured by the user and carry the proxy while running web tests in a secure environment.

LEAPWORK Proxy Settings - detail

The table below explains various proxy type options and their use in LEAPWORK.

Proxy type options  Settings 
No Proxy This is the default, and it means LEAPWORK will not use (disable) any proxy. Use it if your organization does not use any proxy. 
Automatic detection Organizations with automatic proxy detection mechanism should choose this option.
Automatic URL Proxy server URL used in your organization is entered in a text box.
Manual Settings HTTP and HTTPS proxy used in your organization is entered manually in a text box.



Controller Proxy

The LEAPWORK Controller is the server that is responsible for automatically running scheduled tests, gathering results, and storing all automation assets.

The Controller service works in the background to execute tests. In organizations where proxy login is required before running tests externally, users must configure Controller proxy settings. These proxy settings will allow the Controller to automatically log in into proxy while running tests.

For example: If users want to run tests over the internet using proxy, and the proxy requires user login to communicate with external applications, then users should use the Controller proxy as defined below.


LEAPWORK Controller Proxy Settings

The table below explains various proxy type options provided for the LEAPWORK Controller.

Proxy type options  Settings 
Proxy address   The address of the proxy server in your organization 
Domain\User Name  The user name you are using to login into the proxy server. The domain should be provided in case domain name is required in your organization (example: dev\ john, test\john, prod\john)
Password  The password used with the above mention username 
Bypass proxy on local*  If this checkbox is ticked, then the LEAPWORK Controller will not use the above mentioned proxy to test local applications.

Bypass proxy on local: Proxy servers are usually not used to access/test applications residing in local networks as they are more secure and exist within organizational infrastructure. For example: To test an application using a local IP address, such as "http://192.168.101," a proxy server would fail to recognize the address as it is local to the network. Bypass proxy will enable users to circumvent an active proxy server when accessing local address/resources and hence allowing access to above mentioned IP address-based URL.


Studio Proxy

LEAPWORK Studio is the visual designer application that is used to create, debug, and maintain automation cases as well as review results.

Just like the Controller, LEAPWORK Studio also requires proxy settings in case a company has proxy server implementation and the proxy requires login.

Below is an example of proxy settings in Studio.

By default, ‘User settings checkbox’ is ticked which means that the Proxy settings set for the Controller will be used for Studio automatically. 


LEAPWORK Studio Proxy Settings - Using Controller settings

If proxy settings differ from Controller settings, users can define Studio proxy settings as shown below:

LEAPWORK Controller Proxy Settings - custom settings
Note: While executing tests on Agent machines, the proxy will be passed by either Studio or Controller whichever is used to trigger the test on the Agent machine.

For example:

Scenario: My company proxy requires login before I communicate to an external application, and I need to run my web tests from Studios to Sauce Labs.

Resolution: In this case, the user needs to configure proxy details in Studio proxy settings, post that when tests are run pointing to Sauce Lab, LEAPWORK studios will automatically authenticate the proxy and run test on Sauce Labs or any external environment.

Updated June 14, 2018.