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
Per CS/DS Meeting of 11/30/2015: 10.3 minor
fixed in ec9c68d68eabff3784fcf6dabf2c6745734b3c9c
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1302125
Misinterpreted this bug - it is for additional enhancements to the csr-file option implemented in the referenced commit.
Reopening.
Per CS Bug/Ticket Triage held 04/19/2016: 10.4
Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: FUTURE
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1302125) - Custom field version adjusted to None - Issue close_status updated to: None
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2264
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.