pki-bot
commented
3 years ago Comment from edewata (@edewata) at 2016-12-08 03:44:40
See also ticket 2499.
Open pki-bot opened 3 years ago
pki-bot
commented
3 years ago Comment from edewata (@edewata) at 2016-12-08 03:44:40
See also ticket 2499.
pki-bot
commented
3 years ago Comment from mharmsen (@mharmsen) at 2016-12-08 23:47:32
Per PKI Bug Council of 12/08/2016: 10.4 - major
pki-bot
commented
3 years ago Comment from mharmsen (@mharmsen) at 2016-12-08 23:50:33
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1403016
pki-bot
commented
3 years ago Comment from edewata (@edewata) at 2017-02-27 14:12:08
Metadata Update from @edewata:
pki-bot
commented
3 years ago Comment from edewata (@edewata) at 2017-04-07 22:48:23
Metadata Update from @edewata:
pki-bot
commented
3 years ago Comment from mharmsen (@mharmsen) at 2018-04-26 21:07:32
Per 10.5.x/10.6 Triage: FUTURE
alee: missing CLI functionality
This issue was migrated from Pagure Issue #2558. Originally filed by edewata (@edewata) on 2016-12-08 02:44:23:
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.