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.
Description of problem:
When multiple Issuing CAs are supported from a single SCEP Responder, the client SCEP request is required to indicate the ${CA-Identity} value within the SCEP request.
Version-Release number of selected component (if applicable):
How reproducible:
The commands below are part of a bash script, and are reproducible every time.
Request GetCACaps:
Steps to Reproduce:
1. command line request from a bash script
2. sudo /usr/libexec/certmonger/scep-submit -u ${SCEP_RESPONDER} -i ${CA_Identifier} -v –c ${CACaps_file}
3. Note: it is assumed the -c switch identifies a file name that the CACaps file can be written to.
Actual results:
Sending: http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operations=GetCACaps
Expected results:
Expected to send: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operations=GetCACaps&message=poc.bt.com
Request GetCACert (requesting Root CA):
Steps to Reproduce:
1. command line request from a bash script
2. sudo /usr/libexec/certmonger/scep-submit -u ${SCEP_RESPONDER} -i ${RootCA_Identifier} -v –C $ ${RootCA_file}
3. Note: it is assumed the -C switch identifies a file name that the RootCA can be written to.
Actual results:
sending: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operation=GetCACert
Expected results:
Expected to send: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operation=GetCACert&message=root.poc.bt.com
Additional info:
1. See SCEP RFC https://tools.ietf.org/html/draft-nourse-scep-23
2. Appendix C, C1 shows the GetCACaps format
3. 5.2.1 GetCACert indicates the message NVP may be omitted if the SCEP responder, is answering for a single Issuing CA. Commercial CAs tend to answer for multiple Issuing CAs. Hence, this optional value is required.
Regards
Nigel
Description of problem: When multiple Issuing CAs are supported from a single SCEP Responder, the client SCEP request is required to indicate the ${CA-Identity} value within the SCEP request. Version-Release number of selected component (if applicable): How reproducible: The commands below are part of a bash script, and are reproducible every time. Request GetCACaps: Steps to Reproduce: 1. command line request from a bash script 2. sudo /usr/libexec/certmonger/scep-submit -u ${SCEP_RESPONDER} -i ${CA_Identifier} -v –c ${CACaps_file} 3. Note: it is assumed the -c switch identifies a file name that the CACaps file can be written to. Actual results: Sending: http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operations=GetCACaps Expected results: Expected to send: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operations=GetCACaps&message=poc.bt.com Request GetCACert (requesting Root CA): Steps to Reproduce: 1. command line request from a bash script 2. sudo /usr/libexec/certmonger/scep-submit -u ${SCEP_RESPONDER} -i ${RootCA_Identifier} -v –C $ ${RootCA_file} 3. Note: it is assumed the -C switch identifies a file name that the RootCA can be written to. Actual results: sending: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operation=GetCACert Expected results: Expected to send: GET http://onsiteipsec-test.trustwise.com/cgi-bin/pkiclient2.exe?operation=GetCACert&message=root.poc.bt.com Additional info: 1. See SCEP RFC https://tools.ietf.org/html/draft-nourse-scep-23 2. Appendix C, C1 shows the GetCACaps format 3. 5.2.1 GetCACert indicates the message NVP may be omitted if the SCEP responder, is answering for a single Issuing CA. Commercial CAs tend to answer for multiple Issuing CAs. Hence, this optional value is required. Regards Nigel