The basic Sauce Connect Proxy setup is ideal for non-enterprise users with network configurations that require a proxy to open up communication between Sauce Labs and their web or mobile app.
It is also a key step for any Sauce Connect Proxy deployment as a way to verify if you need help from network administrators to complete the configuration. For details, see Validating Your Basic Sauce Connect Proxy Setup.
For information about user configuration settings, see Organization Settings.
- Review Sauce Connect Proxy System and Network Requirements to confirm that your system and network architecture will be compatible with Sauce Connect Proxy.
- Download the appropriate version of Sauce Connect Proxy for your operating system, if you haven't yet. For more information, see Downloading Sauce Connect Proxy.
- Understand what kinds of tests you're running:
- If you're using virtual machines or devices, see the instructions below.
- If you're testing real devices, see Setting Up for Real Device Cloud.
- Know your account details including:
- The url of the datacenter you need to use. For more information, see Data Center Endpoints.
- Your Sauce Labs username and access key, which you can find in Sauce Labs under ACCOUNT > User settings.
Sauce Labs recommends setting all of the values above as environment variables to protect your username and api key from exposure, and also for future convenience.
Once you've downloaded Sauce Connect Proxy, you can validate that it works on your network by completing the following steps:
- Launch a tunnel with the following flags, per the Sauce Connect Proxy Command Line Reference:
$ bin/sc -u $SAUCE_USERNAME -k $SAUCE_ACCESS_KEY -x $SAUCE_DC -i TUNNEL_ID
SAUCE_USERNAMEis the username assigned to your Sauce Labs account.
SAUCE_ACCESS_KEYis the access key associated with that account.
SAUCE_DCis the url of the datacenter you need to use. By default, the
-xoption is not required if you're using the default US West data center. If you're using the Read Device Cloud or the European Data Center,
-x SAUCE_DCis required.
TUNNEL_IDis the identifier or name of the tunnel; for more information, see Using Tunnel Identifiers below.
- Select an appropriate test script. Options might include:
- One of your existing tests, if available.
- An example from Sauce Labs Demonstration Scripts. Follow the instructions to configure the test before proceeding to step 3 below.
- If you are using an tunnel identifier, add the following to the desired capabilities of the test:
TUNNEL_ID is the identifier or name of the tunnel from step 1.
When you see
connected, log in to Sauce Labs and, in the left navigation panel, click TUNNELS. Under Active Tunnels, you should see the tunnel you've just started.
Your next step depends on the outcome of the test:
- If the test isn't working, see Test Not Working below.
- If the test succeeds, there will be a Sauce Connect Proxy icon next to your test.
If you're unable to connect, check with your network administrator about examining firewall settings for roadblocks. For more information, see Allowlisting for Restricted Networks.
Another possible issue is certificate authentication. The server hosting Sauce Connect Proxy may need to connect to Online Certificate Status Protocol (OCSP). See Certificate Handling for more information.
Once you've confirmed that your network is configured for Sauce Connect Proxy, you can start new tunnels as needed.
It is important to be aware of the various options you have for configuring tunnels:
- To use the basic tunnel configuration, you can use the same steps described in VALIDATING to start all subsequent tunnels.
- To use a more advanced or complex configuration, you can use:
As a best practice, Sauce Labs recommends creating a new tunnel for each test suite or build and tearing it down at the end of the test.
|SC Host (Sauce Connect Host)||The machine in your network on which the Sauce Connect Proxy application is running. In this setup, it has a direct connection to the internet.|
|SUT (Site Under Test)||The site that you're testing. It is on the same local network as the SC Host machine.|
|Tunnel VM (Tunnel Virtual Machine)||Virtual machine that hosts Sauce Connect on the Sauce Labs side.|
Sauce Connect Proxy must be on the same network as the website or mobile app being tested, but it is not required to set it up on the same machine.
When launching a Sauce Connect Proxy tunnel for automated web and mobile app tests, you have two options:
- Launch a Sauce Connect tunnel as-is, without identifying it. That default, unnamed tunnel will automatically be used for all automated tests. This can be useful for small organizations with a limited number of tests.
- Assign a name known as a tunnel identifier. To accomplish this, you'll need to launch a tunnel with the
-i (--tunnel-identifier)command to assign the tunnel identifier(s) when starting up Sauce Connect Proxy. Then, you'll need to use the
tunnelIdentifieroption in the desired capabilities of your automated tests (see Using Tunnel Identifiers for more information). This will trigger your tests to request a specific tunnel to run your tests through that tunnel.
Below is an example of how to designate tunnels based on the
tunnelIdentifier option so that it works properly with an automated test.
Launch a new tunnel on the
SC_HOST with the following flags, per the Sauce Connect Proxy Command Line Reference:
- MacOS/Linux Example
- Windows Example
$ sc_download/bin/sc -u $SAUCE_USERNAME -k $SAUCE_ACCESS_KEY -x $SAUCE_DC -i sc-proxy-tunnel
> sc_download\bin\sc.exe -u %SAUCE_USERNAME% -k %SAUCE_ACCESS_KEY% -x %SAUCE_DC% -i sc-proxy-tunnel
- Ensure that your network configuration allows for communication between the
SC Host, the Tunnel VM, and the SUT (site under test). See the basic network configuration diagram for further explanation.
- Select an example from Sauce Labs Demonstration Scripts and follow the instructions to configure the test in your dev environment.
- Navigate to the desired test script and add the following Test Configuration Option in the
Every Sauce Connect Proxy tunnel spins up a fresh virtual machine (VM) that is used only for your tests; VMs are destroyed once the tunnel is closed. A recommended Sauce Connect Proxy best practice is to create a new tunnel for each test suite or build and tear it down at the end of your test.
Sauce Connect Proxy client calls REST API to start a tunnel.
REST API initiates a request to system to create a new Tunnel VM.
REST API tells the Sauce Connect Proxy client DNS name of the Tunnel VM.
Sauce Connect Proxy client makes connection request to Tunnel VM using its DNS name.
At this point, the tunnel is established between the Sauce Connect Client and the Tunnel VM.
Selenium/Appium test code sends an HTTPS request to the VM or Real Device that was created for this test (for example,
Test VM or Device sends this request to Tunnel VM in order to access SUT.
Tunnel VM forwards this request to Sauce Connect Proxy client via the secure tunnel.
Sauce Connect Proxy client forwards the request to Site Under Test (SUT).
Site Under Test returns response to Sauce Connect Proxy client.
Sauce Connect Proxy client sends response to Tunnel VM via secure tunnel.
Tunnel VM sends response to Test VM.
Test VM sends results back to Selenium/Appium Test cloud.
Throughout the lifetime of a tunnel, Sauce Connect Proxy client sends status information to Sauce Labs REST API.