Sauce Labs provides a figure of lineament that assist fasten your testing experience and ensure that your datum and coating are safe while using our cloud platform. One of the most popular features isSauce Connect Proxy—a built-in HTTP proxy server that opens a secure & quot; tunnel & quot; connection for testing between a Sauce Labs practical machine or real device and a site or mobile app host on your local figurer (& quot; localhost & quot;) or behind a corporate firewall. It provides a means for Sauce Labs to firmly access your application or website.

Over last two days, our squad has continually update Sauce Connect with new features, security improvements, and critical bugs fixes related to functionality and execution, including:

• Fixed file descriptor leaks

• Mitigated unexpected clangor

• Enabled support for Apple ’ s best practice for network protection (App Transport Security - ATS) for sites/apps with self signed security

• Improved PAC file parse

• Added validation of of command line comment for tunnel and direct orbit

• Introduced use of certificates signed by a Certificate Authority (CA) rather than self-signed security in Sauce Labs internal tunneling infrastructure

  Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

• Introduced OCSP certificate validation

• Implemented application Notarization on MacOS - Catalina and newer require Sauce Connect guest binary to be Apple notarized

To take advantage of all these improvements, we get been strongly encouraging client to upgrade to the latest stable liberation -. The latest version has be in production without any known major issues.

To help improve the protection posture of Sauce Labs and our users, we recently announced that we will stop support for older Sauce Connect variation. Our plan is to vilipend versions 4.5.0 and below on Dec 31, 2020 and versions 4.6.2.and below on March 31, 2021. These modification impact customer using old, standalone Sauce Connect binaries as well those using old the Sauce Connect binary prepackaged with our OnDemand Jenkins Plugin.

Update Process

Customers who are still habituate an outdated adaptation of Sauce Connect should follow these measure to make the appropriate updates:

• If you use an old, standalone Sauce Connect binary (variation 4.5.0 or below) then please upgrade to Sauce Connect 4.6.2 or above from the. Test the new version in a development or staging environment by running some manual and automated test. If you don ’ t notification any issues then please upgrade your production environment to the new version.

• If you use an old Sauce Connect binary prepackaged with theSauce OnDemand Jenkins plugin(versions 1.187 and below) so delight use Jenkins system configuration to update to the latest OnDemand Jenkins plugin (or version 1.188 or higher).

Best Practice and Future Releases

We regularly ship new characteristic and advance with Sauce Connect client releases. We recommend that customer use the latest version of Sauce Connect released in the last three months and create routine updates to the Sauce Connect client.

In 2021, we are planning to do several fundamental changes in Sauce Connect backend. These changes will necessitate discontinued support for all previous versions of the Sauce Connect guest. In preparation for this modification we strongly promote client to prepare and test processes for all of their environments (dev, stage, and production) that will give them flexibleness to elevate the Sauce Connect client on short observation.

Please contact support @ saucelabs.com if you have any questions or demand additional info.