-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
io.testerra.bup - forward username and password for proxy with username and password #140
Comments
Isn't it possible to pass credentials in the constructor URL? URL apiBaseUrl = new URL("https://user:password@my-proxy");
BrowserUpRemoteProxyManager browserUpRemoteProxyManager = new BrowserUpRemoteProxyManager(apiBaseUrl); |
I think, @jdoeschn means the upstream proxy which requires username/pass. But Mikes solution could also work for them:
|
@martingrossmann : yes, sorry for my incomplete problem description, I mean the upstream proxy. I am currently using |
What kind of authentication is used for the upstream proxy? Is it generally possible to access the proxy via. credentials in the URL? |
Thank you for the fast support! The bugfix solved my problem. |
Problem description
I have to run testerra tests through an https proxy (so the system under test is behind this proxy). The proxy need s username and password for authentication. I need to provide username and password to the https proxy before accessing the SUT.
*Prefered solution
On proxy setup, it should be possible to add credentials (username and passwort) for authentication against web proxies.
Describe alternatives you've considered
I could setup browsermobproxy without testerra, but testerra already has a bup integration - so i'd prefere using it.
Additional context
no additional context.
Maybe it is enough to set in startServer method the parameters (if provided)
startServerUriBuilder.setParameter("proxyUsername", username);
startServerUriBuilder.setParameter("proxyPassword", password);
and add a way to set username and password
The text was updated successfully, but these errors were encountered: