Proxy Support for Oauth2

[mortega89]

Hi there,
here's the situation:
we need to integrate scoold (which is deployed to kubernetes) with Okta as IDP, which is reachable with proxy only with basic auth.

normally, we have this onto the para container:

18 │ 2025-11-06 13:49:39 [ERROR] null 19 │ java.net.UnknownHostException: <<REDACTED>> : System error 20 │ at java.base/java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) 21 │ at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) 22 │ at java.base/java.net.InetAddress.getAddressesFromNameService(Unknown Source) 23 │ at java.base/java.net.InetAddress$NameServiceAddresses.get(Unknown Source) 24 │ at java.base/java.net.InetAddress.getAllByName0(Unknown Source) 25 │ at java.base/java.net.InetAddress.getAllByName(Unknown Source) 26 │ at java.base/java.net.InetAddress.getAllByName(Unknown Source) 27 │ at org.apache.hc.client5.http.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:43) 28 │ at org.apache.hc.client5.http.impl.io.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141) 29 │ at org.apache.hc.client5.http.impl.io.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:447) 30 │ at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:162) 31 │ at org.apache.hc.client5.http.impl.classic.InternalExecRuntime.connectEndpoint(InternalExecRuntime.java:172) 32 │ at org.apache.hc.client5.http.impl.classic.ConnectExec.execute(ConnectExec.java:142) 33 │ at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51) 34 │ at org.apache.hc.client5.http.impl.classic.ProtocolExec.execute(ProtocolExec.java:192) 35 │ at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51) 36 │ at org.apache.hc.client5.http.impl.classic.HttpRequestRetryExec.execute(HttpRequestRetryExec.java:96) 37 │ at org.apache.hc.client5.http.impl.classic.ExecChainElement.execute(ExecChainElement.java:51) .....
so, we've add

http_proxy
https_proxy
no_proxy

to the environment variables and we've add the parameter

Djava.net.useSystemProxies=true

but we got always the same errors.

we also tried to change the commandline by using java vars but it's seems to not support natively the authentication. but the problem it's the same

-Dhttps.proxyHost
-Dhttp.proxyPort=
-Dhttp.nonProxyHosts=

also, we tried to create a parallel javaagent to give global parameters with Username and Password onto the commandline without success.

it's seems that para needs to resolve the dns before all, I do not understand if there's any chance to get para just use a proxy.
Sorry to bother you, any chance to get the outbound proxy feature available or I misunderstand the application completely ?

Thanks

[albogdano]

I think it would best if you mapped the Okta service to localhost using some other tool like nginx. You can connect to the proxy and link it to a port on localhost as described in this post: https://serverfault.com/questions/933145/proxy-a-remote-server-as-localhost