Skip to content
This repository has been archived by the owner on Jan 19, 2021. It is now read-only.

Support for custom flags when starting sauce connect tunnels #199

Open
jtheodore-rent opened this issue Feb 14, 2017 · 3 comments
Open

Support for custom flags when starting sauce connect tunnels #199

jtheodore-rent opened this issue Feb 14, 2017 · 3 comments

Comments

@jtheodore-rent
Copy link

It would be helpful if we could utilize the functionality of Sauce Connect Launcher to pass custom flags through when setting up tunnels via the create_tunnels command.

One blocking issue that I have run into with this is that tunnels launched with this command don't work on Android devices running on OS 4.4 or newer because of the security warning generated when presented with an untrusted application certificate.

From Sauce Support:

"When using Sauce Connect, the Sauce Connect application does a re-encryption in which it takes the original certificate of the site that you are trying to access and re-encrypts it with the CyberVillains certificate. The CyberVillans certificate is not on the list of trusted certificates and this is why you see the security warning appearing.

Thus, avoiding the CyberVillains certificate re-encryption usually solves the problem. For this, all you need to do is start the Sauce Connect Application with the flag "-B all". The "-B all" flag will tell Sauce Connect to avoid the CyberVillains certificate re-encryption in all the sites that you will access during your test."

It would be very helpful to have a way to enable that "-B all" flag when starting my sauce connect tunnels so that I can run tests against SauceLabs' Android emulators with SauceConnect.

Thanks,
John Theodore

@Maciek416
Copy link
Contributor

Hey John, thanks for filing this. This is definitely a missing feature.

We've run into the same issue, but since we've moved on to a static tunnel infrastructure ( using crows-nest ), we've been able to pass these parameters to our tunnel creation process separately. I'm not sure if static tunnels are a valid workaround for you, but if you can't wait for a fix, it might be an option.

@archlichking
Copy link
Contributor

Thanks for the feedback @jtheodore-rent. We have already realized the limitation of current tunnel manager in magellan. Our next step is to embed crows-nest as tunnel manager to replace the current one. It's on its way, but it'll take some time. Please try crows-nest as a standalone tunnel manager if you cannot wait for a fix.

@jtheodore-rent
Copy link
Author

jtheodore-rent commented Feb 14, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants