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
{{ message }}
Repository navigation
ServerRegistry not refreshing certificate information #924
Describe the bug
We are using thrift-mux TLS connections to introduce mTLS between our clients & servers. Recently we switched to dynamic certificate provisioning using cert-manager. These certificates are only valid for a few hours and are rotated frequently. We implemented a custom SslEngineFactory that provides a new SslContext after each reload.
We noticed that /admin/servers/connections/ shows expired certificate dates, because the certificate information does not get updated during the lifetime of a connection.
To Reproduce
Steps to reproduce the behavior:
Create a ThriftMux.client.withTransport.tls()
Provide a SslClientEngineFactory that allows to you update the underlying SslContext
Connect to a server, reload the ssl certificate
Connection is using the new certificate and validation works as expected
ServerRegistry shows outdated certificate information
Expected behavior
The ServerRegistry should show the latest certificate information for a connection.
If needed I can try to create a small POC that shows our setup.
Activity
heligw commentedon Feb 4, 2022
Can you create a small POC to show your setup?
basert commentedon Feb 18, 2022
Hey, sorry for the late reply. Here's how our ReloadingEngineFactory looks like:
It's used in the client by providing an instance of
SslClientConfigurationwhich has the ssl certificate File set.I'll check if I can setup some repo with an example in the next days if needed.