#3002 CRMFPopClient ignores -n option
Closed: migrated by dmoluguw. Opened by mharmsen.

Refer Document: http://pki.fedoraproject.org/wiki/Certificate_Key_Archival
This doc uses -m -n -u -r all in one cli.

CRMFPopClient -v -d test -p SECret.123 -n CN=testuser -f caSigningUserCert -b transport.pem -m $HOSTNAME:8080 -u testuser23 -r testuser23

In runtime, it fails with error:

Request ID: 157
Request Status: rejected
Reason: Request 157 Rejected - Subject Name Not Matched UID=testuser23

-- If we test the same with caUserCert , which uses subject dn format as uid=*.

CRMFPopClient -v -d test -p SECret.123 -n UID=testuser00 -f caDualCert -b transport.pem -m $HOSTNAME:8080 -u testuser23 -r testuser23

It works and a request gets created with CA Agent page but that request has subject dn as:

Certificate Pretty Print

Certificate: 
    Data: 
        Version:  v3
        Serial Number: 0xCDB6EED
        Signature Algorithm: SHA512withRSA - 1.2.840.113549.1.1.13
        Issuer: CN=CA Signing Certificate,OU=pki-ca-Mar8,O=Example-rhcs92-CA
        Validity: 
            Not Before: Monday, March 19, 2018 1:10:49 PM EDT America/New_York
            Not  After: Saturday, September 15, 2018 1:10:49 PM EDT America/New_York
        Subject: UID=testuser23

==> Ideally it should be "UID=testuser00" i.e input provided to option -n

Steps to Reproduce:

Use this document and follow the process http://pki.fedoraproject.org/wiki/Certificate_Key_Archival

Actual results:

failure.

Expected results:

It should work

Per 10.5.x/10.6 Triage: 10.5.x

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1558139
- Custom field type adjusted to None
- Custom field version adjusted 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/3120

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

Metadata