Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1459792[details]
Customer provided patch
Description of problem:
We had recently run into an issue when migrating keys from a legacy TMS CA (CS8) to a NextGen TMS CA (CS9). The CA started fine when built, but after migrating the keys (replacing the temp keys in the HSM with the real ones (same names)) the CA would fail to start indicating that the CA signing key could not be found. The logs show the CA trying to append the HSM OCS to a nickname that already contains an HSM OCS:
[authorityMonitor]: readAuthority: new entryUSN = 35254
[authorityMonitor]: CertificateAuthority.init(MAIN, ca)
[authorityMonitor]: CertificateAuthority:initSigUnit: ca cert found
[authorityMonitor]: CertificateAuthority: initSigUnit 1- setting mIssuerObj and mSubjectObj
[authorityMonitor]: CA SigningUnit.init(ca, ca.signing, NSS-OCS:caSigningCert cert-tms-ca-1)
[authorityMonitor]: SigningUnit: Logging into token NSS-OCS
[authorityMonitor]: SigningUnit: Loading certificate NSS-OCS:NSS-OCS:caSigningCert cert-tms-ca-1
[authorityMonitor]: SigningUnit: Unable to find certificate NSS-OCS:NSS-OCS:caSigningCert cert-tms-ca-1
[authorityMonitor]: CA signing key and cert not (yet) present in NSSDB
[authorityMonitor]: Starting KeyRetrieverRunner thread
[authorityMonitor]: CertificateAuthority init: initRequestQueue
[authorityMonitor]: returnConn: mNumConns now 3
[KeyRetrieverRunner-a82c78da-9ce0-42d8-b410-2072aa8a6fdc]: Unable to read key retriever class from CS.cfg: Property features.authority.keyRetrieverClass missing value
[KeyRetrieverRunner-a83c78da-9ce0-42d8-b410-2072aa8a6fdc]: Retrying in 10 seconds
We are not sure why this only happens after migrating the keys and not when the CA is built.
Version-Release number of selected component (if applicable):
This issue is seen in the 10.5.1 CA packages. (RHCS 9.3)
How reproducible:
Very
Steps to Reproduce:
1. Build CA with temporary keys
2. Migrate over permanent keys with same names
3. Attempt to start CA
Actual results:
CA Fails to start stating the signing key cannot be found.
Expected results:
CA Should start as expected.
Additional info:
GD will be making the following change to the CA code:
- base/ca/src/com/netscape/ca/SigningUnit.java
o Checks if the key nickname already has the token name prefix, and does not apply the prefix again in this case.
See attached diff file for details. The change will be provided to DISA and they will merge it into the master branch.
Comment 2Endi Sukma Dewata
2018-08-29 15:22:09 UTC
Hi, the patch does not contain the author's name and email address. Does the customer want to include theirs? Otherwise, the patch will be committed with the name/email of the person that will push the patch. Thanks.
This was already discussed on phone with them today. We will create a plain "code name" for such integration. Going forward, all such integration will carry the same code name.
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.
https://access.redhat.com/errata/RHBA-2020:1078
Created attachment 1459792 [details] Customer provided patch Description of problem: We had recently run into an issue when migrating keys from a legacy TMS CA (CS8) to a NextGen TMS CA (CS9). The CA started fine when built, but after migrating the keys (replacing the temp keys in the HSM with the real ones (same names)) the CA would fail to start indicating that the CA signing key could not be found. The logs show the CA trying to append the HSM OCS to a nickname that already contains an HSM OCS: [authorityMonitor]: readAuthority: new entryUSN = 35254 [authorityMonitor]: CertificateAuthority.init(MAIN, ca) [authorityMonitor]: CertificateAuthority:initSigUnit: ca cert found [authorityMonitor]: CertificateAuthority: initSigUnit 1- setting mIssuerObj and mSubjectObj [authorityMonitor]: CA SigningUnit.init(ca, ca.signing, NSS-OCS:caSigningCert cert-tms-ca-1) [authorityMonitor]: SigningUnit: Logging into token NSS-OCS [authorityMonitor]: SigningUnit: Loading certificate NSS-OCS:NSS-OCS:caSigningCert cert-tms-ca-1 [authorityMonitor]: SigningUnit: Unable to find certificate NSS-OCS:NSS-OCS:caSigningCert cert-tms-ca-1 [authorityMonitor]: CA signing key and cert not (yet) present in NSSDB [authorityMonitor]: Starting KeyRetrieverRunner thread [authorityMonitor]: CertificateAuthority init: initRequestQueue [authorityMonitor]: returnConn: mNumConns now 3 [KeyRetrieverRunner-a82c78da-9ce0-42d8-b410-2072aa8a6fdc]: Unable to read key retriever class from CS.cfg: Property features.authority.keyRetrieverClass missing value [KeyRetrieverRunner-a83c78da-9ce0-42d8-b410-2072aa8a6fdc]: Retrying in 10 seconds We are not sure why this only happens after migrating the keys and not when the CA is built. Version-Release number of selected component (if applicable): This issue is seen in the 10.5.1 CA packages. (RHCS 9.3) How reproducible: Very Steps to Reproduce: 1. Build CA with temporary keys 2. Migrate over permanent keys with same names 3. Attempt to start CA Actual results: CA Fails to start stating the signing key cannot be found. Expected results: CA Should start as expected. Additional info: GD will be making the following change to the CA code: - base/ca/src/com/netscape/ca/SigningUnit.java o Checks if the key nickname already has the token name prefix, and does not apply the prefix again in this case. See attached diff file for details. The change will be provided to DISA and they will merge it into the master branch.