Proxy credentials don´t work within browser

[ZNicoZ]

A proxy with credentials won´t be transmitted to the browser (chrome)

HTTP_PROXY=http://username:[email protected]

WGET within the container was able to resolve the proxy.

Workaround at a customer was to use another proxy which authenticates against the actual proxy but was used by sakuli.

[svettwer]

The issue is caused by an inconsistent proxy handling in Sakuli. Provided environment variables are not considered during test case execution, as Selenium requires a specific proxy config when creating the webdriver.

E.g:

selenium.proxy.proxyType=manual
selenium.proxy.httpProxy="http://foobar:[email protected]:3128"
selenium.proxy.sslProxy="https://foobar:[email protected]:3128"

Workaround
A workaround would be to configure the proxy twice. Once as container environment variables and once as properties in sakuli.properties

Possible solutions

1. Check HTTP(S)_PROXY environment variables when creating the driver and overwrite whatever comes from sakuli.properties
2. During container startup : echo "selenium.proxy.httpProxy=${HTTP_PROXY}" >> ${SAKULI_EXECUTION_DIR}/sakuli.properties

I'd prefer the first solution as it would be a consistent convention not only in the container but also on test hosts.

[svettwer]

For development and testing, I recommend https://github.com/svettwer/dev-proxy

[svettwer]

We agreed to go with attempt No. 1

[svettwer]

Summary of the last two hours:

1. The workaround was just working by accident. For some reason, the proxy is not used at all if credentials are provided in the config. They are passed to selenium but seems to be discarded afterwards.
2. Selenium seems to be unable to process proxy credentials without additional plugins.

[svettwer]

Todo: Find a way so that selenium uses proxy credentials.

Open upstream issues:

• Please offer a solution for basic authentication SeleniumHQ/selenium#6644
• Missing support for HTTP authentication prompts w3c/webdriver#385

[svettwer]

Sakuli Workaround:

selenium.proxy.proxyType=manual
selenium.proxy.httpProxy=127.0.0.1:3128
selenium.proxy.sslProxy=127.0.0.1:3128

• Insert creds with native ui interaction

[svettwer]

Workaround available; fix not possible => 🧊