Bug 584983
| Summary: | certmonger should assume the IPA CA type when tracking an existing certificate | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rob Crittenden <rcritten> |
| Component: | certmonger | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | nalin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | certmonger-0.21-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-12-03 15:34:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Agreed. Targeting for 0.21. certmonger-0.21-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc13 certmonger-0.21-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc12 certmonger-0.21-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc11 certmonger-0.21-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc13 certmonger-0.21-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc12 certmonger-0.21-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.21-1.fc11 certmonger-0.22-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.22-1.fc11 certmonger-0.22-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.22-1.fc13 certmonger-0.22-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update certmonger'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/certmonger-0.22-1.fc12 certmonger-0.23-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. certmonger-0.23-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. certmonger-0.23-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: I have an existing SSL server certificate for mod_nss and I'd like certmonger to manage it for me. This certificate was generated by an IPA server. So I start the tracking: # ipa-getcert start-tracking -n Server-Cert -d /etc/httpd/alias New tracking request "20100422200339" added. But it doesn't show up in my list # ipa-getcert list <nothing> It does show up in plain old getcert # getcert list Request ID '20100422200339': status: MONITORING stuck: no key pair storage: type=NSSDB,location='/etc/httpd/alias',nickname=Server-Cert certificate: type=NSSDB,location='/etc/httpd/alias',nickname=Server-Cert issuer: CN=Certificate Authority,O=IPA subject: CN=lion.example.com,O=IPA expires: 20101019155216 eku: id-kp-serverAuth track: yes auto-renew: yes This is apparently because the CA type isn't set to IPA. I think start-tracking should force the CA type to IPA. Version-Release number of selected component (if applicable): certmonger-0.18-1.fc12.x86_64