<commit_before>{
  title: "Sauce Connect",
  description: "Documentation for Sauce Connect",
  category: "Reference",
  index: 0
}

Sauce Connect is a secure tunneling app which allows you to execute tests securely when testing behind firewalls via a secure connection between Sauce Labs’ client cloud and your environment.

##  When should I use Sauce Connect?

You should use Sauce Connect whenever you’re testing an app behind a firewall. Sauce Connect is **not** required to execute scripts on Sauce.

You can also use Sauce Connect:

- as an alternative to whitelisting
- as a means of filtering traffic in your records (e.g. for Google Analytics)
- as a means of monitoring network traffic
- as a way to stabilize network connections (detecting/re-sending dropped packets)

##  Getting started

**Before you begin** 
1. Make sure port 443 can be opened for outbound connections. 
2. Get Sauce Connect v4:
<ul>
<li><a href="https://saucelabs.com/downloads/sc-latest-osx.zip"><i class="fa fa-apple"></i> Download Sauce Connect for OS X</a><br>
</li><li><a href="https://saucelabs.com/downloads/sc-latest-win32.zip"><i class="fa fa-windows"></i> Download Sauce Connect for Windows</a><br>
</li><li><a href="https://saucelabs.com/downloads/sc-latest-linux.tar.gz"><i class="fa fa-linux"></i> Download Sauce Connect for Linux</a><br>
</li><li>(If you're looking for Sauce Connect v3, you download it <a href="https://saucelabs.com/downloads/Sauce-Connect-latest.zip">here</a>.)<br>
</li>
</ul>
3. Unzip (or untar).  
4. Open a command prompt.
5. Go to the install directory and start sc:

```bash
bin/sc -u sauceUsername -k sauceAccessKey
```

6. When you see "connected", you are ready to go! 
7. Read our take on security: [Security best practices][1]

##  How is Sauce Connect secured?

Though starting up a tunnel using Sauce Connect may take a few seconds, our tunneling method allows for the highest possible security. We spin up a secure tunnel sandbox environment for each tunnel connection in order to provide greater tunnel security and isolation from other customers.

Data transmitted by Sauce Connect is encrypted through industry-standard TLS, using the AES-256 cipher. Sauce Connect also uses a caching web proxy to minimize data transfer. To read more about security on Sauce, read our [security white paper][2].

Within your infrastructure, Sauce Connect needs access to the application under test, but can be firewalled from the rest of your internal network. We recommend running Sauce Connect in a firewall DMZ, on a dedicated machine, and setting up firewall rules to restrict access from that DMZ to your internal network.


![How is Sauce Secured][3]

##  Setup process

The initial outbound connect created by Sauce Connect is over port 443 to *.saucelabs.com. The response to this request contains instructions which Sauce Connect will use to establish a secure tunnel between Sauce Connect and Sauce Labs client cloud. Now that Connect has it’s instructions it will create another outbound connect to *.saucelabs.com also over 443. Once the connection is established all traffic between Sauce Labs and Sauce Connect will be multiplexed over a single encrypted TLS connection.

##  Teardown process

Once Sauce Connect is asked terminated (typically via ctrl-c), a call will be made from Sauce Connect to the REST API with instructions to terminate the tunnel VM. Sauce Connect will continue to poll the REST API until the tunnel VM has been halted and deleted.

##  System requirements
<commit_msg>Updated SC image, Fixes #2<commit_after>{
  title: "Sauce Connect",
  description: "Documentation for Sauce Connect",
  category: "Reference",
  index: 0
}

Sauce Connect is a secure tunneling app which allows you to execute tests securely when testing behind firewalls via a secure connection between Sauce Labs’ client cloud and your environment.

##  When should I use Sauce Connect?

You should use Sauce Connect whenever you’re testing an app behind a firewall. Sauce Connect is **not** required to execute scripts on Sauce.

You can also use Sauce Connect:

- as an alternative to whitelisting
- as a means of filtering traffic in your records (e.g. for Google Analytics)
- as a means of monitoring network traffic
- as a way to stabilize network connections (detecting/re-sending dropped packets)

##  Getting started

**Before you begin** 
1. Make sure port 443 can be opened for outbound connections. 
2. Get Sauce Connect v4:
<ul>
<li><a href="https://saucelabs.com/downloads/sc-latest-osx.zip"><i class="fa fa-apple"></i> Download Sauce Connect for OS X</a><br>
</li><li><a href="https://saucelabs.com/downloads/sc-latest-win32.zip"><i class="fa fa-windows"></i> Download Sauce Connect for Windows</a><br>
</li><li><a href="https://saucelabs.com/downloads/sc-latest-linux.tar.gz"><i class="fa fa-linux"></i> Download Sauce Connect for Linux</a><br>
</li><li>(If you're looking for Sauce Connect v3, you download it <a href="https://saucelabs.com/downloads/Sauce-Connect-latest.zip">here</a>.)<br>
</li>
</ul>
3. Unzip (or untar).  
4. Open a command prompt.
5. Go to the install directory and start sc:

```bash
bin/sc -u sauceUsername -k sauceAccessKey
```

6. When you see "connected", you are ready to go! 
7. Read our take on security: [Security best practices][1]

##  How is Sauce Connect secured?

Though starting up a tunnel using Sauce Connect may take a few seconds, our tunneling method allows for the highest possible security. We spin up a secure tunnel sandbox environment for each tunnel connection in order to provide greater tunnel security and isolation from other customers.

Data transmitted by Sauce Connect is encrypted through industry-standard TLS, using the AES-256 cipher. Sauce Connect also uses a caching web proxy to minimize data transfer. To read more about security on Sauce, read our [security white paper][2].

Within your infrastructure, Sauce Connect needs access to the application under test, but can be firewalled from the rest of your internal network. We recommend running Sauce Connect in a firewall DMZ, on a dedicated machine, and setting up firewall rules to restrict access from that DMZ to your internal network.


![How is Sauce Secured](/images/reference/sauce-connect/sc.png)

##  Setup process

The initial outbound connect created by Sauce Connect is over port 443 to *.saucelabs.com. The response to this request contains instructions which Sauce Connect will use to establish a secure tunnel between Sauce Connect and Sauce Labs client cloud. Now that Connect has it’s instructions it will create another outbound connect to *.saucelabs.com also over 443. Once the connection is established all traffic between Sauce Labs and Sauce Connect will be multiplexed over a single encrypted TLS connection.

##  Teardown process

Once Sauce Connect is asked terminated (typically via ctrl-c), a call will be made from Sauce Connect to the REST API with instructions to terminate the tunnel VM. Sauce Connect will continue to poll the REST API until the tunnel VM has been halted and deleted.

##  System requirements

{'fraction_non_alphanumeric': 0.07605633802816901, 'fraction_numerical': 0.007605633802816901, 'mean_word_length': 4.5174825174825175, 'pattern_counts': {'":': 0, '<': 59, '<?xml version=': 0, '>': 59, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 16, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7040548', 'n_tokens_mistral': 1961, 'n_tokens_neox': 1800, 'n_words': 992}