Removing subject DN requirement when submitting a CSR via CLI

[pki-bot]

This issue was migrated from Pagure Issue #1705. Originally filed by edewata (@edewata) on 2015-11-26 00:33:41:

• Assigned to edewata (@edewata)

---

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-11-30 21:24:22

Per CS/DS Meeting of 11/30/2015: 10.3 minor

[pki-bot]

Comment from ftweedal (@frasertweedale) at 2016-01-12 02:56:11

fixed in ec9c68d68eabff3784fcf6dabf2c6745734b3c9c

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-01-26 23:35:17

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1302125

[pki-bot]

Comment from ftweedal (@frasertweedale) at 2016-01-27 01:37:16

Misinterpreted this bug - it is for additional enhancements to the csr-file option implemented in the referenced commit.

Reopening.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-04-21 00:31:39

Per CS Bug/Ticket Triage held 04/19/2016: 10.4

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-12-01 21:20:28

Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor

[pki-bot]

Comment from edewata (@edewata) at 2017-02-27 14:10:19

Metadata Update from @edewata:

• Issue assigned to edewata
• Issue set to the milestone: FUTURE

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-18 20:07:47

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-18 20:07:47

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