Unable to whitelist domains to be omitted from SSL bumping

[nickalto]

I'm currently running into an issue trying to whitelist domains from Sauce's SSL bumping (https://wiki.saucelabs.com/display/DOCS/Troubleshooting+Sauce+Connect).

With the following configuration options in my wdio.conf.js file I have been unable to have the provided domains whitelisted when testing locally with Sauce.

sauceConnect: true,
sauceConnectOpts: {
    tunnelIdentifier: xxxxx,
    connectRetries: 3,
    directDomains: [xxxxxx],
    noSslBumpDomains: [`maps.googleapis.com`]
},

I have tried the following configurations with no success:

    '--no-ssl-bump-domains': ['maps.googleapis.com']

    '-B':['maps.googleapis.com']

    noSslBumpDomains: ['all']

    noSslBumpDomains: ['*.googleapis.com']

I'm currently running into this with v1.2.2 and wdio-sauce-service v4.0

Has anyone had success omitting domains from being SSL bumped using wdio / sauce?

I have verified sauce-connect-launcher is successfully converting noSslBumpDomains into the proper --no-ssl-bump-domains required in the docs. When logging the processed options in sauce-connect-launcher.js I see:

[
    ...
    '--no-ssl-bump-domains',
    'maps.googleapis.com',
    ...
]

But sifting through the logs I get no mention of ssl-bump-domains being white listed, and the requested resources do not get whitelisted when testing on Sauce.

Any help would be appreciated.

[tobeliketree]

I'm seeing this as well. We're passing our host similarly and have tried similar combinations like @nickalto above and the whitelisting does not seem to be taking place as expected.

sauceConnectOpts: { noSslBumpDomains: '*.photoshelter.com' },

Conversations with sauceLabs help the only solution that has worked for us in testing was passing the -B option to the sauce connect command line arguments. We're rather let this happen at the wide config level.

@nickalto Did you ever get this to work using WDIO?