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.
Test Build:
==========
rpm -qa pki-*
pki-console-10.4.1-5.el7pki.noarch
pki-javadoc-10.4.1-11.el7.noarch
pki-symkey-10.4.1-11.el7.x86_64
pki-tools-10.4.1-11.el7.x86_64
pki-base-10.4.1-11.el7.noarch
pki-kra-10.4.1-11.el7.noarch
pki-server-10.4.1-11.el7.noarch
pki-ocsp-10.4.1-10.el7pki.noarch
pki-base-java-10.4.1-11.el7.noarch
pki-ca-10.4.1-11.el7.noarch
pki-tps-10.4.1-10.el7pki.x86_64
pki-tks-10.4.1-10.el7pki.noarch
pki-core-debuginfo-10.4.1-11.el7.x86_64
Test Cases:
-----------
Test Case 1:
===========
When cmc.revokeCert.sharedSecret.class and cmc.sharedSecret.class are not present in CS.cfg
1. Install CA with new bits i.e pki-ca-10.4.1-11.el7.noarch.
2. Verified by default CS.cfg doesn't have:
cmc.revokeCert.sharedSecret.class=com.netscape.cms.authentication.SharedSecret
cmc.sharedSecret.class=com.netscape.cms.authentication.SharedSecret
3. perform one CMC test and see how it works if above two properties are missing from CA's CS.cfg.
<snip output>
Number of controls is 1
Control #0: CMCStatusInfo
OID: {1 3 6 1 5 5 7 7 1}
BodyList: 0
Status String: Proof-of-Identification Verification Failed after verifyIdentityProofV2
OtherInfo type: FAIL
</snip output>
Test Case 2: Add the two properties manually in CS.cfg and restart CA.
===========
1. Add the two properties manually in CS.cfg and make sure CMC tests worked.
2. Features tested and verified as part of this testing:
-- User-signed CMC requests Example (with PopLinkWitnessV2)
-- Self-Signed CMC Request Example (with IdentityProofV2)
-- User-signed CMC request Without POP (Encrypted POP / Decrypted POP)
-- User-Signed CMC Renewal Request
I have tried to cover basic sanity testing for CMC.Please revert if you think any other test case I need to cover as part of this testing.
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/RHSA-2017:2335