#1506 PKCS12Export tool returns error
Closed: Fixed None Opened 8 years ago by aakkiang.

PKCS12Export tool returns org.mozilla.jss.crypto.ObjectNotFoundException.

Steps to Reproduce:

1. Have a nssdb with certificates and keys
2. Execute PKCS12Export tool

Example:
# PKCS12Export  -debug -d . -o ALL_ROLE_CERTS.p12 -p ./password  -w ./password2
PKCS12Export: Reading database password from ./password
PKCS12Export: Logging into security token
PKCS12Export: Reading PKCS #12 password from ./password
PKCS12Export: Generating PKCS #12 data
PKCS12Export:  * Certificate: ROOTCA_agentE
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: KRA3_agentE
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: ocsp3admincert
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: OCSP3_agentE
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: TKS1_agentE
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: tps1admincert
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: TPS1_agentE
PKCS12Export:    Private key exists
PKCS12Export:  * Certificate: casigningcert
org.mozilla.jss.crypto.ObjectNotFoundException
        at org.mozilla.jss.CryptoManager.findPrivKeyByCertNative(Native Method)
        at
org.mozilla.jss.CryptoManager.findPrivKeyByCert(CryptoManager.java:1344)
        at
com.netscape.cmstools.PKCS12Export.generatePKCS12Data(PKCS12Export.java:227)
        at com.netscape.cmstools.PKCS12Export.exportData(PKCS12Export.java:301)
        at com.netscape.cmstools.PKCS12Export.main(PKCS12Export.java:369)

Expected results:

Export should be successful, and ALL_ROLE_CERTS.p12 file gets created.

Fixed in master: 46dd3b8b536a515ec743001d6f797556f4fffb98

Metadata Update from @aakkiang:
- Issue assigned to edewata
- Issue set to the milestone: 10.2.6

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

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.

Login to comment on this ticket.

Metadata