#969 pki user-cert-del gives an exception when the required options are switched positions
Closed: migrated by dmoluguw. Opened by rpattath.

[root@sigma tmp.tPCcRUL4tm]# pki user-cert-del
usage: user-cert-del

I gave the Cert ID first and then the User ID as follows

[root@sigma tmp.tPCcRUL4tm]# pki -d /opt/rhqa_pki/certs_db/ -n CA_adminV -c redhat123 -t ca user-cert-del "2;84;CN=CA Signing Certificate,O=lab.eng.rdu.redhat.com Security Domain;UID=testuser2,E=testuser2@example.org,CN=Test user2,OU=Engineering,O=Example,C=US" testuser2

ProcessingException: Unable to invoke request


Per discussions, targeted 10.2 Backlog

[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1232059 (Red Hat Certificate System)

Per IRC discussion with alee, I confirmed that this is 10.4.

Metadata Update from @rpattath:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field lowhangingfruit adjusted to vakwetu: X
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue priority set to: minor (was: major)
- Issue set to the milestone: FUTURE (was: UNTRIAGED)

Metadata Update from @mharmsen:
- Issue assigned to edewata

The user ID and cert ID are positional arguments, so the input is invalid, but we probably should provide a more meaningful error message.

Per 10.5.x/10.6 Triage: FUTURE

edewata: negative case

RHBZ: CLOSED UPSTREAM

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1232059)

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/1535

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