temporalio / temporalio/sdk-rust
[Feature Request] Support disabling host verification
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 161
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 67
Description
Is your feature request related to a problem? Please describe.
Related to the python client issue https://github.com/temporalio/sdk-python/issues/463
The current client implementation requires a CA cert verification. However in the case of internal communication where encryption in transit is required, but it is impractical to implement a CA for a local cluster this makes us jump through hoops to attempt to get things working.
Describe the solution you'd like
A desired implementation would be that if the CA cert and domain are not entered in the TLSConfig that the CA cert is not verified and TLS is still used. Could implement a warning message to let people know this is happening or optionally add another option that removes this warning or enables this behavior.
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 by reading the linked Python client issue and tracing how the Rust client's TLSConfig handles CA certificates and domain verification. Determine the existing TLS configuration and warning patterns before defining the change; done means TLS can remain enabled without CA or domain verification when those fields are omitted, with the requested warning or option behavior covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100