-
Notifications
You must be signed in to change notification settings - Fork 316
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
Disabling hostname checking for connecting via SSL #258
Comments
You can set the right authority via the builder:
|
@lburgazzoli thanks - looks like I need to use a SNAPSHOT to get access to that. |
@lburgazzoli How should one set the authority correctly when there are multiple endpoints, each with distinct name and certificate? |
I think there was a discussion about this issue on grpc-java about this so I need to check what solution has been implemented and reflect it on jetcd but I had no time so far. The issue is on how the grpc-java NameResolver. |
Re-opening as this is still not usable. Authority needs to be set per endpoint. |
@agarman I'm not sure about what we can do on jetcd side, see the following conversations: |
@agarman @kingpong I think I need to wait for grpc/grpc-java#4469 to be implemented to provide a solution. |
@lburgazzoli understood |
This issue is stale because it has been open 60 days with no activity. |
I updated the library version to the latest version (0.5.3) to solve this problem |
Attempting to connect to compose.io etcd service using example in SssTest.java. It looks like compose.io uses certificates that do not
matchDNS
. Is there a way to disableHostnameChecker
exposed byClientBuilder
orGrpcSslContexts
?The text was updated successfully, but these errors were encountered: