-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ServerRegistry not refreshing certificate information #924
Comments
Can you create a small POC to show your setup? |
Hey, sorry for the late reply. Here's how our ReloadingEngineFactory looks like:
It's used in the client by providing an instance of
I'll check if I can setup some repo with an example in the next days if needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
ThriftMux.client.withTransport.tls()
SslClientEngineFactory
that allows to you update the underlyingSslContext
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.
The text was updated successfully, but these errors were encountered: