#3140 Key retrieve with RequestID is getting failed with error (PKIException: Internal Server Error)
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by cipherboy.

Description of problem:
key-retrieve request should be successful with RequestID.
Issue : Key retrieve with RequestID is getting failed with error (PKIException: Internal Server Error) but retrieve with keyID working fine. RequestID option is showing under help suggestion but not on man page.

Version-Release number of selected component (if applicable):
10.5.9-7.el7_6

How reproducible:

[root@ibm-x3650m4-02-vm-02 ~]# pki -c SECret.123 -n "PKI KRA Administrator" -P https -h localhost -p 20443 key-archive --passphrase "foobar15" --clientKeyID "test_15"
------------------------
Archival request details
------------------------
  Request ID: 0x36d90da8c7486c
  Key ID: 0x5
  Type: securityDataEnrollment
  Status: begin
[root@ibm-x3650m4-02-vm-02 ~]# pki -c SECret.123 -n "PKI KRA Administrator" -P https -p 20443 key-request-review --action approve 0x5
------
Result
------
  Request ID: 0x5
  Key ID: 0x1
  Type: enrollment
  Status: complete
[root@ibm-x3650m4-02-vm-02 ~]# pki -c SECret.123 -n "PKI KRA Administrator" -P https -p 20443 key-retrieve --requestID 0x5
PKIException: Internal Server Error
[root@ibm-x3650m4-02-vm-02 ~]# pki -c SECret.123 -n "PKI KRA Administrator" -P https -p 20443 key-retrieve --keyID 0x1
------------------------
Retrieve Key Information
------------------------
  Key Algorithm: 1.2.840.113549.1.1.1
  Key Size: 1024
  Nonce data: /p83dLyii6CUgC8Z4pd0/g==
  Actual archived data: MIICdgIBADANBgkqhkiG9w0BAQEFAASCAmAwggJcAgEAAoGBAL1RgAEdhq5hEs8rs0dBpE8QPcaPdz8L3rOlXXIyz92OF/wqO2UNkHv57geTK1q9GlPlPovSa/w5gu+976Idw/qR3wJcgnE6ByJnxBIqm2/PnWfqIkRBGQBoS18+cfnOcpVDxTvARO87McQdOx2ndnKN2TYwhNuIe+XltxLys/zlAgMBAAECgYBN/KXDT9tsOBbcer8Ganb6DtGz2uOfeA9MZ6F/6oiQVvlwaiE/dn//Yix4uFpSrbWLu9KxHIRZSYOzqMVvPd29xDpPzIzwpSEfsv5DdD694BoExjsD0btNwhLXZfZ+nYN5jYTf+NebGgw1xz5/XWL3mgpnKDvBSU3xcQtFi/7GHQJBAN0/4OhSftuK4ODop5I6cDNNe/QZEfPTP7L2h8KgeRnFHm3a4+De4lPOukrsJ4ywf1KNuvzN9BbUunkMdyzRVjMCQQDbDbc7V4tBXeAj2a1FhzPVGDj092W1hbUz0p+ClwS7JNH7VsMMBJlTE7pkORuZgRGwf7poE+6rSSI8bAmAmliHAkEAvSXLRVKhmVdVgXHlMKI9Id7wRXLZYjYLkxgoYD+IyHs41Hn5r1lc7IEjysGx3hlWAGGiplX8gzhCYxJBIFOm+QJATNYGy53tjsQq9uhHyvedysVwVRziZEW+Ras/oELwueQ0c4D/cZu7XFSzMKyHbdTEK7Dh5df4A8TnaWJMAvwgyQJAO/B4qnrWu5nCHPGQLn6yKsV5OGj5b+qOSTZxpwFVQhtCCSH1/AnKuuN9ubPWQQqp7lqM+cEht+3KlKLDhm+kSg==
[root@ibm-x3650m4-02-vm-02 ~]#

[root@ibm-x3650m4-02-vm-02 dirsrv]# pki -c SECret.123 key-retrieve --help
usage: key-retrieve [OPTIONS...]
    --keyID <Key Identifier>                        Key Identifier for the secret to be recovered.
    --requestID <Recovery Request Identifier>       Request Identifier for  approved recovery request

Steps to Reproduce:
1. pki -c SECret.123 -n "PKI KRA Administrator" -P https -h localhost -p 20443 key-archive --passphrase "foobar15" --clientKeyID "test_15"
2. pki -c SECret.123 -n "PKI KRA Administrator" -P https -p 20443 key-request-review --action approve 0x5
3. pki -c SECret.123 -n "PKI KRA Administrator" -P https -p 20443 key-retrieve --requestID 0x5

Actual results:
PKIException: Internal Server Error

Expected results:
Success

Additional info:
requestID parameter with pki is showing in help page but not in man page


Metadata Update from @cipherboy:
- 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=1658030
- Custom field type adjusted to None
- Custom field version adjusted to None

4 years ago

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

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)

3 years ago

Login to comment on this ticket.

Metadata