-
Notifications
You must be signed in to change notification settings - Fork 39
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
Setting https proxy via Configuration with auth doesn't work for TSL #106
Comments
What kind of parameters are you configuring via Configuration to enable proxying? What type of authentication is your proxy using? Are you using the same proxy for proxying both HTTP and HTTPS requests? For example, when configuring proxying via the following:
then TSL HTTPS requests (as I understood HTTP requests already work for you for TSP and OCSP) seem to work without a problem via a proxy that requests Basic auth. |
We set both http and https and user and password using these mentioned setters, but it doesn't work - we get errors only TSL requests in logs, but no specifics besides IOException. If we disable proxy, everything works again. We actually found an inconvenient way to disable proxy for TSL only using the internal registry. |
By "internal registry", do you mean the ConfigurationRegistry instance inside the org.digidoc4j.Configuration class? Did you try configuring everything else but the TSL proxy via the connection-type-specific methods?
Where ExternalConnectionType stands for one of We are looking into trying to reproduce the issue locally, but with no luck so far. |
Unfortunately, it is not possible to set proxy for everything except TSL, e.g. |
But the original problem remains: if TSL proxy is set (both http & https), it doesn't use the httpProxyUser/httpProxyPassword, so all requests result in 407 responses |
TSL tries to use the proxy without auth and fails.
TSP and OCSP respect proxy auth.
The text was updated successfully, but these errors were encountered: