#2781 pki-server ca-cert-request-find cli --cert and --cert-file does not accept .pem file
Closed: migrated by dmoluguw. Opened by mharmsen.

Amol K. wrote:

I found some issue with pki-server ca-cert-request-find CLI.
I try the following commands, but i did not get expected result.

Steps to Reproduce:

1. # pki-server ca-cert-request-find -i topology-02-CA --cert admin_cert.pem
-----------------
0 entries matched
-----------------
2. # pki-server ca-cert-request-find -i topology-02-CA --cert ca_cert.pem
-----------------
0 entries matched
-----------------
3. # pki-server ca-cert-request-find -i topology-02-CA --cert-file ca_cert.pem
-----------------
0 entries matched
-----------------

Actual results:

It return 0 entries matched.

Expected results:

It should accept .pem file. And shows the certificate request.

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1469239
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)
- Issue set to the milestone: FUTURE (was: 10.5)

Per 10.5.x/10.6 Triage: FUTURE

edewata: usability issue. there's a workaround.

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

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