ARROW-5643: [FlightRPC] Add ability to override SSL hostname checking #4608
Conversation
ghost
mentioned this pull request
pitrou
left a comment
pitrou
left a comment
There was a problem hiding this comment.
Can you rebase? The TLS tests in test_flight.py were fixed recently on master.
cpp/src/arrow/flight/client.h
Outdated
There was a problem hiding this comment.
I don't think we need to mark it insecure?
There was a problem hiding this comment.
I can shorten the name, but I'd at least like to stress that it's potentially a footgun in production.
cpp/src/arrow/flight/flight-test.cc
Outdated
There was a problem hiding this comment.
Hmm... interesting. The certificate error is not raised at connect time?
There was a problem hiding this comment.
gRPC doesn't actually try to make a connection until an RPC is issued, generally.
cpp/src/arrow/flight/flight-test.cc
Outdated
There was a problem hiding this comment.
Is there an error message we can check?
There was a problem hiding this comment.
There is, but I've been bitten elsewhere by messages that changed across gRPC versions...once #4484 lands, I'd rather we wrap and expose the gRPC error code + error message instead of just a message (and maybe map error codes to a set of Flight codes).
|
Rebased, shortened name to "override_hostname". |
python/pyarrow/tests/test_flight.py
Outdated
There was a problem hiding this comment.
Ok... you have to pass the connect_args as above, otherwise flight_server may be stuck in a loop trying to reconnect.
|
hey @pitrou this probably isn't the place for this question but I can't find an issue that matches my problem more closely. I was wondering if there was good example of deploying a python flight server/service into kubernetes. I'm using the pyarrow cookbook for the flight server and am getting hung up on some gotcha in the service or deployment config, or maybe something with the URL. any help or guidance would be much appreciated |
|
@patcollis34 I don't have an answer, I suggest you ask on the user mailing-list. |
Adds the ability to override hostname checks, so you can connect to localhost over TLS but still verify that the certificate is for some other domain. Example: when deploying on Kubernetes with headless services, clients connect directly to backend services and do load balancing themselves. Thus all instances of an application must present a certificate for the same hostname. To do health checks in such an environment, you can't connect to the TLS hostname (which may resolve to a different instance); you need to connect to localhost, and override the hostname check. Also needs apache/arrow-testing#5 Author: David Li <[email protected]> Closes apache#4608 from lihalite/flight-tls-java and squashes the following commits: 581fc75 <David Li> Add ability to override SSL hostname checking
3 participants
Adds the ability to override hostname checks, so you can connect to localhost over TLS but still verify that the certificate is for some other domain.
Example: when deploying on Kubernetes with headless services, clients connect directly to backend services and do load balancing themselves. Thus all instances of an application must present a certificate for the same hostname. To do health checks in such an environment, you can't connect to the TLS hostname (which may resolve to a different instance); you need to connect to localhost, and override the hostname check.
Also needs apache/arrow-testing#5