Bug 1955633 - Recovery of Keys migrated to latest version of KRA fail to recover and result in Null Point Exception [rhel-7.9.z] [NEEDINFO]
Summary: Recovery of Keys migrated to latest version of KRA fail to recover and result...
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.9
Assignee: Jack Magne
QA Contact: PKI QE
URL:
Whiteboard:
Depends On:
Blocks: 1960745
TreeView+ depends on / blocked
 
Reported: 2021-04-30 14:55 UTC by Chris Zinda
Modified: 2021-05-17 08:19 UTC (History)
7 users (show)

Fixed In Version: pki-core-10.5.18-14.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1960745 (view as bug list)
Environment:
Last Closed:
Target Upstream Version:
prisingh: needinfo? (jmagne)


Attachments (Terms of Use)

Description Chris Zinda 2021-04-30 14:55:50 UTC
Description of problem:
Keys Migrated to the latest version of KRA stored the same storage certificate using the older 3des are not recoverable and result in a Null Point Exception


Version-Release number of selected component (if applicable):
pki-ca-10.5.18

How reproducible:
Very.

Steps to Reproduce:
Anytime a recovery attempt is made against a Key Record that does not have MetaInfo attributes in the database


Actual results:
Null Pointer exception (attached logs)

Expected results:
To properly capture the keys

Additional info:
Anytime a recovery attempt is made against a Key Record that does not have MetaInfo attributes in the database

https://github.com/dogtagpki/pki/blob/v10.5.18/base/server/cmscore/src/com/netscape/cmscore/dbs/KeyRecord.java#L509

mMetaInfo does not exist for Legacy Key Records so it cannot parse it for a value. 

What information can you provide around timeframes and the business impact?
Prevents the Recovery to token, and the Recovery to p12 for any key that does not have the metaInfo attribiutes.


Note You need to log in before you can comment on or make changes to this bug.