-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Enhance client-side gRPC TLS configuration #39091
Conversation
Previously, utilizing JKS or P12 keystores and truststores in gRPC clients was restricted due to limitations inherent in legacy gRPC-Java-based clients. However, this commit expands upon the existing configuration by introducing support for JKS and P12 in the Quarkus (Vert.x based) gRPC client. This commit also extends the tests for both clients and servers using various certificate formats and configuration (like mTLS)
Status for workflow
|
🙈 The PR is closed and the preview is expired. |
Status for workflow
|
@geoand we can follow the same model for the rest client (until I introduce the registry) |
Cool, I'll resume me PR based on this work |
Actually I am going to wait for the big rename to be merged so we don't mess things up |
Previously, utilizing JKS or P12 keystores and truststores in gRPC clients was restricted due to limitations inherent in legacy gRPC-Java-based clients. However, this commit expands upon the existing configuration by introducing support for JKS and P12 in the Quarkus (Vert.x based) gRPC client.
This commit also extends the tests for both clients and servers using various certificate formats and configuration (like mTLS)