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:

To archive the key we need to set this attributes in the KRA instance's CS.cfg file on HSM machine.
kra.allowEncDecrypt.archive = false
kra.allowEncDecrypt.recovery = false


Version-Release number of selected component (if applicable):
10.5.1-5.el7

How reproducible:
Always

Steps to Reproduce:
1. pki -d /root/nssdb/ -c SECret.123 -p 20080 client-cert-request "UID=testuser1,CN=testuser1" --type crmf
2. pki -d /root/nssdb/ -c SECret.123 -p 20080 -n "PKI CA Administrator for Example.Org" -v ca-cert-request-review --action approve 17
3.

Actual results:

BadRequestException: Request Sending DRM request failed check KRA log for detail Rejected - {1}

Expected results:
It should be successful. And key gets archived in the HSM.


Additional info:

I'm a little confused.  I though that when using the HSM, you had to set the parameters to True (not false).

I added a bit more of a description of the feature here:

http://pki.fedoraproject.org/wiki/Aes-feature-description

Per CS/DS Meeting of 20180122, closing as NOTABUG.

I open this Bugzilla as Fraser suggested in comment[1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1460019#c18

Fraser is confused I think:

See the link I mentioned:

http://pki.fedoraproject.org/wiki/Aes-feature-description

I was confused :)

Was not aware that the HSMs did not support key wrapping with AES.
But one day they will, surely...?