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.
Bug 1484359 - Lightweight CA key replication fails (regressions)
Summary: Lightweight CA key replication fails (regressions)
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Fraser Tweedale
QA Contact: Michal Reznik
Marc Muehlfeld
Depends On:
Blocks: 1486870
TreeView+ depends on / blocked
Reported: 2017-08-23 10:48 UTC by Fraser Tweedale
Modified: 2020-10-04 21:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The Certificate System CA key replication now works correctly A previous update to one of the key unwrapping functions introduced a requirement for a key usage parameter which was not being supplied at the call site, which caused lightweight Certiciate Authority (CA) key replication to fail. This bug has been fixed by modifying the call site so that it supplies the key usage parameter, and lightweight CA key replication now works as expected.
Clone Of:
: 1486870 (view as bug list)
Last Closed: 2018-04-10 17:00:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
verification_steps (3.04 KB, text/plain)
2018-01-22 13:23 UTC, Michal Reznik
no flags Details

System ID Private Priority Status Summary Last Updated
Fedora Pagure 7387 0 None None None 2018-02-06 15:42:28 UTC
Fedora Pagure freeipa issue 7387 0 None None None 2018-02-06 15:44:05 UTC
Github dogtagpki pki issues 2916 0 None None None 2020-10-04 21:35:33 UTC
Red Hat Product Errata RHBA-2018:0925 0 None None None 2018-04-10 17:01:04 UTC

Description Fraser Tweedale 2017-08-23 10:48:06 UTC
Description of problem: lightweight CA replication fails with a

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

How reproducible: always

Steps to Reproduce:
1. Install FreeIPA and replica with CA.
2. Create a new lightweigth ca (`ipa ca-add`)

Actual results: Key replication to the replica fails with the following log output

[23/Aug/2017:20:39:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Running ExternalProcessKeyRetriever
[23/Aug/2017:20:39:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: About to execute command: [/usr/libexec/ipa/ipa-pki-retrieve-key, caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92, f25-1.ipa.local]
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Importing key and cert
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Caught exception during cert/key import
        at org.mozilla.jss.pkcs11.PK11KeyWrapper.unwrapSymmetric(PK11KeyWrapper.java:458)
        at com.netscape.cmsutil.crypto.CryptoUtil.unwrap(CryptoUtil.java:2536)
        at com.netscape.cmsutil.crypto.CryptoUtil.importPKIArchiveOptions(CryptoUtil.java:2317)
        at com.netscape.ca.CertificateAuthority$KeyRetrieverRunner._run(CertificateAuthority.java:3597)
        at com.netscape.ca.CertificateAuthority$KeyRetrieverRunner.run(CertificateAuthority.java:3502)
        at java.lang.Thread.run(Thread.java:748)
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Retrying in 576 seconds

Expected results: key replication to the replica succeeds; log output will be like:

[23/Aug/2017:20:36:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Running ExternalProcessKeyRetriever
[23/Aug/2017:20:36:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: About to execute command: [/usr/libexec/ipa/ipa-pki-retrieve-key, caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92, f25-1.ipa.local]
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Importing key and cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Reinitialising SigningUnit
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority:initSigUnit: ca cert found
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority: initSigUnit 1- setting mIssuerObj and mSubjectObj
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: ca.signing Signing Unit nickname caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got token Internal Key Storage Token by name
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Found cert by nickname: 'caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92' with serial number: 15
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: converted to x509CertImpl
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got private key from cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got public key from cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: got signing algorithm RSASignatureWithSHA256Digest
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CA signing unit inited
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: cachainNum= 0
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got CA chain from JSS.
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Shared OCSP signing unit inited
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got OCSP chain from JSS.
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CA First signing algorithm is SHA1withRSA
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority: initSigUnit - setting mIssuerObj and mSubjectObj
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got CA name CN=test1
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Adding self to authorityKeyHosts attribute
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: In LdapBoundConnFactory::getConn()
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: masterConn is connected: true
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: getConn: conn is connected true
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: getConn: mNumConns now 1

Additional info:

Comment 2 Fraser Tweedale 2017-08-23 10:55:57 UTC
Upstream ticket: https://pagure.io/dogtagpki/issue/2796
Gerrit review: https://review.gerrithub.io/375318

Comment 3 Matthew Harmsen 2017-08-29 23:37:12 UTC
ftweedal pushed the changes:

    Pushed to master: 33ff29c893b2e0ad13a80f59acb197a7375b7ed9
    Pushed to ORIGIN_10_4_BRANCH: 606027b188fee6d20c17323d7c464d6630024a20

Comment 8 Michal Reznik 2018-01-22 13:22:28 UTC
Verified on:


Comment 9 Michal Reznik 2018-01-22 13:23:33 UTC
Created attachment 1384441 [details]

Comment 11 errata-xmlrpc 2018-04-10 17:00:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.