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.
DescriptionMatthew Harmsen
2016-01-26 21:35:16 UTC
Currently when submitting a CSR via CLI the user is still required to specify a request type and a subject DN:
{{{
$ pki ca-cert-request-submit \
--profile caUserCert \
--csr-file testuser.csr \
--request-type pkcs10 \
--subject UID=testuser,O=EXAMPLE
}}}
To improve usability, the CLI should obtain the request type and subject DN from the CSR itself. The server should also obtain the information from the CSR directly.
The client may display the request data for confirmation:
{{{
$ pki ca-cert-request-submit --profile caUserCert --csr-file testuser.csr
Certificate request:
Request type : PKCS #10
Subject:
UID : testuser
Organization : EXAMPLE
Key Type : RSA
Key Size : 2048
...
Submit certificate request (Y/n)?
}}}
There should also be an option to skip the confirmation:
{{{
$ pki ca-cert-request-submit --profile caUserCert --csr-file testuser.csr -y
}}}
Currently when submitting a CSR via CLI the user is still required to specify a request type and a subject DN: {{{ $ pki ca-cert-request-submit \ --profile caUserCert \ --csr-file testuser.csr \ --request-type pkcs10 \ --subject UID=testuser,O=EXAMPLE }}} To improve usability, the CLI should obtain the request type and subject DN from the CSR itself. The server should also obtain the information from the CSR directly. The client may display the request data for confirmation: {{{ $ pki ca-cert-request-submit --profile caUserCert --csr-file testuser.csr Certificate request: Request type : PKCS #10 Subject: UID : testuser Organization : EXAMPLE Key Type : RSA Key Size : 2048 ... Submit certificate request (Y/n)? }}} There should also be an option to skip the confirmation: {{{ $ pki ca-cert-request-submit --profile caUserCert --csr-file testuser.csr -y }}}