-
Confirm with your Firewall and Proxy teams that the list of IP ranges specified in [1] are opened on the corporate side. I would imagine they were done at the time when Desktop was implemented, but it’ll save a lot of head scratching to confirm in advance.
-
In parallel with Step 1, you’ll need to download the Sauce Connect executable (also found in [1]). You’ll need to make sure that wherever you run it from, it’ll have network access to #1 above.
-
I’ve attached a sample Sauce Connect config file specifically for mobile. Be sure to tweak it to match your environment, specifically the
tunnel-domains
entry to tunnel your corporate traffic. -
Configure a start up script (Windows or Linux) to start Sauce Connect using the specified config file. Here’s an example on Linux:
./sc --user=${SAUCE_RDC_USERNAME} --api-key=${SAUCE_RDC_ACCESS_KEY} --config-file sc.mobile.yml
The SAUCE_RDC_USERNAME is the user ID you use to sign into https://app.testobject.com. Your SAUCE_RDC_ACCESS_KEY can be found by signing into https://app.testobject.com, clicking on the “head” in the upper right corner and select Account Settings. The User API Key is the key you want to supply to Sauce Connect.
[1] https://wiki.saucelabs.com/display/DOCS/Basic+Sauce+Connect+Proxy+Setup