[ARROW-10105] [FlightRPC] Add client option to disable certificate validation with TLS

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: C++, FlightRPC, Java, Python
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/26119
• Assignee: James Duong
• Reporter: James Duong
• Created: 26/Sep/20 09:40
• Updated: 11/Jan/23 08:11
• Resolved: 10/Oct/20 11:27

Description

Users of Flight may want to disable certificate validation if they want to only use encryption. A use case might be that the Flight server uses a self-signed certificate and doesn't distribute a certificate for clients to use.

This feature would be to add an explicit option to FlightClient.Builder to disable certificate validation. Note that this should not happen implicitly if a client uses a TLS location, but does not set a certificate. The client should explicitly set this option so that they are fully aware that they are making a connection with reduced security.

Issue Links

• links to: GitHub Pull Request #8325

Sub-Tasks

• [Java][FlightRPC] Add client option to disable server verification: Resolved
• [Python][C++][FlightRPC] Add client option to disable server validation: Resolved