Use a trusted CA for Redis certificate
- Dominant language
- No language data
- Stars
- 225
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
### Required Terms
- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreement](https://www.salesforce.com/company/program-agreement/)
### What service(s) is this request for?
Redis
### Tell us about what you're trying to solve. What challenges are you facing?
Support for Redis < 6 is scheduled to end on April 30. And Redis 6 instances on Heroku Redis are requiring the usage of TLS but using a self-signed certificate. This self-signed certificate means that the client code is forced to disable the certificate validation. This makes it harder to use the built-in Redis integrations of frameworks as they might not easily allow to disable that validation.
It would be great if Heroku Redis could use a TLS certificate that is trusted by the root stores available on dynos.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.