The tool CRMFPopClient currently requires one to supply needed options to do key archival. One should be allowed to do no key arhival as key archival is an option to CRMF, not a requirement.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1585866 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue assigned to cfu - Issue priority set to: blocker - Issue set to the milestone: 10.5
Up for review https://review.gerrithub.io/#/c/dogtagpki/pki/+/413875
Metadata Update from @cfu: - Issue priority set to: None (was: blocker) - Issue set to the milestone: None (was: 10.5)
Metadata Update from @mharmsen: - Issue priority set to: blocker - Issue set to the milestone: 10.5
https://review.gerrithub.io/#/c/dogtagpki/pki/+/413875
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/3151
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.