Anonymous | Login | 2024-12-21 23:56 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0014581 | ClearOS | app-certificate-manager - Certificate Manager | public | 2017-05-01 17:20 | 2017-05-18 08:02 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | feature | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | 7.3.1 Updates | Fixed in Version | 7.3.1 Updates | ||||||
Summary | 0014581: Create certificate manager state file | ||||||||
Description | The Certificate Manager needs to keep track of deployed certificates. For example, consider the case where we have created third party certificates for www.example.com and: 1) imported the certs into the Certificate Manager 2) deployed the certs in the default web server If we use symlinks to point Apache to the files stored in the Certificate Manager, then we need to make sure these files are not deleted. If not, Apache will refuse to start. Alternatively, we can create copies of the cert files and place them inside an Apache subdirectory. This solves the delete problem, but creates a new issue: what happens when the certificates are renewed? The Certificate Manager would need to re-copy those renewed certificates to the Apache subdirectory. In the end, both design methods require some kind of "state" file. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0005631) user2 2017-05-09 12:50 |
This tracker issue discussion is interesting: https://github.com/certbot/certbot/issues/1473 [^] Let's go with the symlink option with the Debian-like ssl-cert group (if needed). |