oxidecomputer / oxidecomputer/omicron
Prevent last working TLS certificate from being deleted
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Change Description
We should prevent operators from deleting the last working TLS certificate. Currently, we continue to serve expired certificates to prevent locking operators out. However, they are able to delete that certificate before creating a new one. This block them from creating a new certificate and require Oxide intervention to "un-delete" the certificate in CRDB to allow them to create the new certificate.
Expected Behavior
Operators are not able to delete the last certificate.
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 the certificate deletion API and the existing handling of the last working certificate; done means deletion is rejected when it would remove the final certificate, with coverage for the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100