[Bug/Feature Request]: Rotating self-signed SSL certificates cannot be updated after a rotation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 491
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
We have 20+ on-prem and cloud-based small standalone Redis databases, mainly for query caching and local queues.
They are all secured with self-signed SSL client certs that are automatically rotated every 30 days.
Every time this rotation happens, all devs need to copy-paste 3 certificates for every Redis db into the RedisInsight Windows GUI.
As these certs are recreated in-place, keeping the same filename and network location, using cert paths should solve this issue, but there is no option for cert path, just cert contents.
As you moved in version 2.6x and 2.70 into Local Storage storage instead of a connections.db or config.json we can't even automate this.
Can you please consider allowing cert paths?
Thanks!
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
The issue names no files or tests. Start by tracing Redis connection certificate settings and the Local Storage handling described in the report. Done means the rotated certificate workflow is supported without repeated GUI copy-paste, with coverage for the relevant connection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, typescript
- Domain
- database, desktop, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100