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 1469447 - CC: CMC: check HTTPS client authentication cert against CMC signer
Summary: CC: CMC: check HTTPS client authentication cert against CMC signer
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Christina Fu
QA Contact: Asha Akkiangady
Petr Bokoc
URL:
Whiteboard:
Depends On: 1460764
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-11 09:44 UTC by Jaroslav Reznik
Modified: 2018-03-14 10:06 UTC (History)
7 users (show)

Fixed In Version: pki-core-10.4.1-12.el7_4
Doc Type: Enhancement
Doc Text:
This enhancement adds an SSL client authentication certificate check against the CMC signer for CMC requests.
Clone Of: 1460764
: 1518175 (view as bug list)
Environment:
Last Closed: 2017-09-05 11:25:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Test_combinations (9.77 KB, application/vnd.oasis.opendocument.spreadsheet)
2017-08-23 11:04 UTC, Geetika Kapoor
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2575 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-09-05 15:17:55 UTC

Description Jaroslav Reznik 2017-07-11 09:44:11 UTC
This bug has been copied from bug #1460764 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 3 Geetika Kapoor 2017-08-23 11:03:12 UTC
Test build:
------------
rpm -qa pki-ca
pki-ca-10.4.1-12.el7_4.noarch

Test Case 1: Testing done for HttpClient enabled with client mode and secure port.
Test case 2: Testing for above test case 1 with self signed is done.
Test case 3: Testing for above test case 1 with user signed is done.
Test case 4: Testing is done for different combinations and attached in Excel(Test_combinations)

Test Steps:
==========

1. Follow steps mentioned in https://pki.fedoraproject.org/wiki/PKI_10.4_CMC_Feature_Update_%28RFC5272%29#User-Signed_CMC_Renewal_Request. 
2. Run PKCS10Client -d . -p SECret.123 -n "cn=Test74z4,uid=letstest"  -o user-signed/pkcs10.req

Make sure it is successful and output should look like:

Keypair private key id: 4ee9aee7bfffc155c798475e57d6c86653e21ef4

-----BEGIN CERTIFICATE REQUEST-----
MIICcjCCAVoCAQAwLTEYMBYGCgmSJomT8ixkAQEMCGxldHN0ZXN0MREwDwYDVQQDDAhUZXN0NzR6NDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALXYpuzOXCvC5kL4VQG0TGyhlS8jo2B1pEs7tvcscdNuB3N/ESmMN2ORot/fhki/UXH+R4iFa95OToqGbAG2aoLSRcTNWcmp20fxCoQctEQzQrgCyQi5P/MGFkqGL2Q++N2j46xw41S1SdWLaH4SRgtVAP4jFW2l76pru5hMXIe4I3tVqNj4qn08inbnugbDVPdIA2wD0f9Ru8qJ6v6WyRJCD5wANtFD4aQNEkkUkjsfkpS0Auy2Mke3leOtX+Nm8jhAR1rXcre7lR4wg2uYScX/ITzbKIqLVk1/k6pIEtVhMElSOEoHYNpor9w2eJ3XKxABTIPTBD6LJ1vNLh5ZcAcCAwEAAaAAMA0GCSqGSIb3DQEBCwUAA4IBAQAoDUTv/pXKaaR8JR5JTkmPPSGaB0bQA827gbRUEbAi2Y7Z4/ci1k3TroDM1AOET0yM2dXCahNzRJMIUBO3vKiTQbgnCFd1T2xhWAbPtqz9z9Q4mApyq8QwH01KmPjWPJCIKanSgofdsbSsLrcY/UBNuRK3hCzB9c2KR4VF85SZ+Xq27FTlafT85b/rfPhRKfeFqgRt5s9i3uWH3EreNAv2pItoPk4U6/OX0uhm84oh8cUhSqsT5yMWtwUYvNEbQSvqLBL/zWN9mMozRBgfTaIh8hT7y7NGkecFquxVR/knMXLLWA0Et4gdq7o6t5CA8LrOusklCwks71QrOrVvl5gz
-----END CERTIFICATE REQUEST-----

3. Replace private key generated above into the cmc file.
4. Run the cmc file using CMCRequest.
5. Run HttpClient.
6. Check using CMCresponse a correct response is getting generated.
7. Goto CA Agent page and see that a certificate is getting generated.
8. Make sure that the newly signed certificate which gets created have:

AKI of newly signed certificate (c1) == user signing certificate AKI (c2) == SKI of  CA cert used to sign c2

Comment 4 Geetika Kapoor 2017-08-23 11:04:06 UTC
Created attachment 1317058 [details]
Test_combinations

Comment 6 errata-xmlrpc 2017-09-05 11:25:02 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.

https://access.redhat.com/errata/RHBA-2017:2575


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