RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

There should be some mechanism using which while doing pkispawn we should be able request for certificate issuance using CMC .
This way, a user has flexibility to generate certificates using CMC during run time without going through the manual process of generating subsystem certificate as mentioned in 
https://pki.fedoraproject.org/wiki/PKI_10.4_CMC_Feature_Update_%28RFC5272%29#Examples_.28User_Certificates.29

Maybe some property that we could set in CS.cfg file of subsystems and while contacting CA they request for CMC certs.

Version-Release number of selected component (if applicable):


How reproducible:

rpm -qa pki-ca
pki-ca-10.4.1-12.el7_4.noarch

Steps to Reproduce:
1. Refer https://pki.fedoraproject.org/wiki/PKI_10.4_CMC_Feature_Update_%28RFC5272%29#Examples_.28User_Certificates.29
2.
3.

Actual results:


Expected results:



Additional info:

cfu: maybe future if deemed necessary.  Although in most cases, people probably just go with the default PKCS#10.  I expect people to follow the cmc installation only if they go strictly with CC.

Cloned Pagure Issue #2991 - FUTURE

Clsoing Bug as Upstream