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
The example above uses client certificate auth. Hence the proxy in this setup is transparent for TLS (typical setup in our company). Nevertheless, the problem exists also when disabling the client certificate authentication. In this case, I could get TLS for the http sink to work by loading the CA cert into the openssl certificate store. It seems, that the implementation of the proxy simply forgets all TLS settings in case the proxy is enabled.
The configuration given below is actually a shell script which creates a self signed CA, signs certificates and runs three docker containers:
graph LR;
client(vector with demo log source and http sink)--port 3128 -->proxy(squid);
proxy-- port 10443 -->server(vector with http source and console sink);
Digging through the hyper-proxy implementation I found out that the ProxyConnector does not make use of the TlsConnector including the user supplied settings. Instead, a new TlsConnector is created in the constructor.
A note for the community
Problem
When enabling a proxy for the http sink, the TLS handshake with an internal PKI always fails (see debug output of the client below).
Simulating the same request using openssl succeeds:
The example above uses client certificate auth. Hence the proxy in this setup is transparent for TLS (typical setup in our company). Nevertheless, the problem exists also when disabling the client certificate authentication. In this case, I could get TLS for the http sink to work by loading the CA cert into the openssl certificate store. It seems, that the implementation of the proxy simply forgets all TLS settings in case the proxy is enabled.
The configuration given below is actually a shell script which creates a self signed CA, signs certificates and runs three docker containers:
Thanks in advance!
Configuration
Version
0.23.0
Debug Output
Example Data
No response
Additional Context
References
The text was updated successfully, but these errors were encountered: