[root@sigma tmp.tPCcRUL4tm]# pki user-cert-show usage: user-cert-show <User ID> <Cert ID> [OPTIONS...] --encoded Base-64 encoded --output <file> Output file --pretty Pretty print
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-show "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
UserNotFoundException: User 2 not found
User testuser2 exists with fullName="Test User2"
While the error message is slightly confusing (only in the fact that it says "User 2"), I would expect to receive an error like "user not found" if you swap the order of arguments. You can't switch the order of the "User ID" and "Cert ID" options. It's treating the first option as a user ID, and it can't find a user based on that input. What else is expected?
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=1232056 (Red Hat Certificate System)
Per Bug Triage of 05/03/2016: CLOSE INVALID
Metadata Update from @rpattath: - Issue set to the milestone: UNTRIAGED
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/1534
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.
Login to comment on this ticket.