Certificate renewal can be done via CLI, but currently the procedure is not very straightforward since it requires a number of detailed steps involving multiple tools, which discourages its usage.
The following pages describe some improvements that can be done to simplify it by merging some steps and hiding some complexities:
This improvement is important since currently the CA UI and some third-party applications (e.g. IPA/certmonger) are still using the legacy servlets for renewals which are harder to use and troubleshoot directly. With a better certificate renewal procedure it would be easier to migrate the UI and third-party applications so the legacy servlets can eventually be dropped.
See also ticket #2499.
Per PKI Bug Council of 12/08/2016: 10.4 - major
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1403016
Metadata Update from @edewata: - Issue set to the milestone: 10.4
Metadata Update from @edewata: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: 10.4)
Per 10.5.x/10.6 Triage: FUTURE
alee: missing CLI functionality
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2678
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.