Skip to content
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

ARROW-5643: [FlightRPC] Add PKCS#1 format keys for testing Flight in Java #5

Merged
merged 1 commit into from Jun 19, 2019
Merged

ARROW-5643: [FlightRPC] Add PKCS#1 format keys for testing Flight in Java #5

merged 1 commit into from Jun 19, 2019

Conversation

ghost
Copy link

@ghost ghost commented Jun 18, 2019

Turns out Netty can only read PKCS#1 format private keys.

@ghost
Copy link
Author

ghost commented Jun 18, 2019

Part of apache/arrow#4608

@wesm wesm merged commit a674dac into apache:master Jun 19, 2019
@wesm
Copy link
Member

wesm commented Jun 19, 2019

@lihalite since I squashed you may have to update the submodule hash in your PR

@ghost
Copy link
Author

ghost commented Jun 19, 2019

Thanks, will do!

pitrou pushed a commit to apache/arrow that referenced this pull request Jun 24, 2019
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 #4608 from lihalite/flight-tls-java and squashes the following commits:

581fc75 <David Li> Add ability to override SSL hostname checking
alamb pushed a commit to apache/arrow-rs that referenced this pull request Apr 20, 2021
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 #4608 from lihalite/flight-tls-java and squashes the following commits:

581fc7582 <David Li> Add ability to override SSL hostname checking
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants