Feature: Support for custom TLS configuration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 415
- Forks
- 83
- Avg merge
- 2h 20m
- Merged PRs (30d)
- 3
Description
Currently, the Qdrant client uses default TLS settings (like native roots) when connecting over HTTPS. Users operating in environments with specific security requirements, such as those using custom CAs, cannot configure the client's TLS handshake process.
I've implemented a solution that adds an optional tls_config field to QdrantConfig, allowing users to provide their own tonic::transport::ClientTlsConfig for fine-grained control over TLS settings: https://github.com/qdrant/rust-client/pull/271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the QdrantConfig definition and review pull request 271, which contains the proposed implementation. Check how the optional tonic::transport::ClientTlsConfig is passed into HTTPS connection setup, and verify that custom CA and other TLS settings are honored without changing default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100