Reload keystore/truststore during runtime
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
API ML loads the keystore and truststore during application startup. This works well in environments where certificates have a long lifetime (e.g., one year). However, certificate authorities are gradually reducing the validity period of issued certificates, with the new target being just 47 days. This would cause additional downtime of API ML. For example, see DigiCert’s schedule: https://www.digicert.com/blog/tls-certificate-lifetimes-will-officially-reduce-to-47-days
Describe the solution you'd like
Allow API ML to dynamically reload private key and certificate from keyring/keystore.
Describe alternatives you've considered
Switch to full AT-TLS.
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 tracing where API ML loads the keystore and truststore during application startup; the issue names no specific files or tests. Define the runtime reload entry point and verify that updated private keys and certificates from the keyring or keystore are used without application downtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100