You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users running WDIO and @wdio/browserstack-service using a corporate proxy requiring root certificate are unable to add this config in wdio.conf.js browserstack service section.
Describe the solution you'd like.
Add configuration corresponding to the Browserstack Local Binary CLI flag --use-ca-certificate to the opts property for browserstack service and apply it when executing binary along with already existing config options like proxyHost and ProxyPort.
Describe alternatives you've considered.
Local binary can be started manually in terminal with the cert as argument for --use-ca-certificate but this is a bad workaround at its best.
We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!
Is your feature request related to a problem?
Users running WDIO and @wdio/browserstack-service using a corporate proxy requiring root certificate are unable to add this config in wdio.conf.js browserstack service section.
Describe the solution you'd like.
Add configuration corresponding to the Browserstack Local Binary CLI flag --use-ca-certificate to the opts property for browserstack service and apply it when executing binary along with already existing config options like proxyHost and ProxyPort.
Describe alternatives you've considered.
Local binary can be started manually in terminal with the cert as argument for --use-ca-certificate but this is a bad workaround at its best.
Additional context
https://www.browserstack.com/docs/local-testing/binary-params
Code of Conduct
The text was updated successfully, but these errors were encountered: