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

Enhanced TLS configuration #820

Open
ianbotsf opened this issue Mar 10, 2023 · 0 comments
Open

Enhanced TLS configuration #820

ianbotsf opened this issue Mar 10, 2023 · 0 comments
Labels
enhancement New feature or request no-auto-closure We do not want this issue to be automatically closed.

Comments

@ianbotsf
Copy link
Contributor

ianbotsf commented Mar 10, 2023

(split from #661)

Add additional APIs to configure HTTP engine TLS context.

This may be at the common HttpClientEngineConfig level or at individual engine config level depending on what makes sense.

Possible knobs:

  • min TLS version (handled in TLS Configuration #661)
  • CA certs (trust manager)
  • Cipher preferences
  • Certificate pinning
  • Host name verifier

Not every engine will support all of these or even if they do may make it difficult to map a common API to.

After these changes are made, coordinate updates to the Developer Guide to clarify how to configure TLS.

Once certificate management is available, complete the HTTP test suite to verify that TLS min versions are working correctly on local test servers with self-signed certificates (see TODO in ConnectionTest.kt).

@ianbotsf ianbotsf added the enhancement New feature or request label Mar 10, 2023
@ianbotsf ianbotsf added the no-auto-closure We do not want this issue to be automatically closed. label Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-auto-closure We do not want this issue to be automatically closed.
Projects
None yet
Development

No branches or pull requests

1 participant