[
https://issues.apache.org/jira/browse/ARROW-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lidavidm updated ARROW-5643:
----------------------------
Fix Version/s: (was: 0.14.0)
1.0.0
> [Flight] Add ability to override hostname checking
> --------------------------------------------------
>
> Key: ARROW-5643
> URL: https://issues.apache.org/jira/browse/ARROW-5643
> Project: Apache Arrow
> Issue Type: Improvement
> Components: FlightRPC
> Reporter: lidavidm
> Assignee: lidavidm
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> We should add 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
