#2796 lightweight CA replication fails with a NullPointerException:
Closed: fixed 6 years ago Opened 6 years ago by ftweedal.

How reproducible: always

Steps to Reproduce:

  1. Install FreeIPA and replica with CA.
  2. Create a new lightweigth ca (ipa ca-add)

Actual results: Key replication to the replica fails with the following log output

[23/Aug/2017:20:39:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Running ExternalProcessKeyRetriever
[23/Aug/2017:20:39:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: About to execute command: [/usr/libexec/ipa/ipa-pki-retrieve-key, caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92, f25-1.ipa.local]
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Importing key and cert
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Caught exception during cert/key import
java.lang.NullPointerException
        at org.mozilla.jss.pkcs11.PK11KeyWrapper.unwrapSymmetric(PK11KeyWrapper.java:458)
        at com.netscape.cmsutil.crypto.CryptoUtil.unwrap(CryptoUtil.java:2536)
        at com.netscape.cmsutil.crypto.CryptoUtil.importPKIArchiveOptions(CryptoUtil.java:2317)
        at com.netscape.ca.CertificateAuthority$KeyRetrieverRunner._run(CertificateAuthority.java:3597)
        at com.netscape.ca.CertificateAuthority$KeyRetrieverRunner.run(CertificateAuthority.java:3502)
        at java.lang.Thread.run(Thread.java:748)
[23/Aug/2017:20:39:20][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Retrying in 576 seconds

Expected results: key replication to the replica succeeds; log output will be like:

[23/Aug/2017:20:36:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Running ExternalProcessKeyRetriever
[23/Aug/2017:20:36:19][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: About to execute command: [/usr/libexec/ipa/ipa-pki-retrieve-key, caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92, f25-1.ipa.local]
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Importing key and cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Reinitialising SigningUnit
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority:initSigUnit: ca cert found
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority: initSigUnit 1- setting mIssuerObj and mSubjectObj
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: ca.signing Signing Unit nickname caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got token Internal Key Storage Token by name
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Found cert by nickname: 'caSigningCert cert-pki-ca bbb070b9-becc-4a1c-a55b-7ce96b31ed92' with serial number: 15
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: converted to x509CertImpl
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got private key from cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Got public key from cert
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: got signing algorithm RSASignatureWithSHA256Digest
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CA signing unit inited
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: cachainNum= 0
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got CA chain from JSS.
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Shared OCSP signing unit inited
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got OCSP chain from JSS.
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CA First signing algorithm is SHA1withRSA
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: CertificateAuthority: initSigUnit - setting mIssuerObj and mSubjectObj
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: in init - got CA name CN=test1
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: Adding self to authorityKeyHosts attribute
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: In LdapBoundConnFactory::getConn()
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: masterConn is connected: true
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: getConn: conn is connected true
[23/Aug/2017:20:36:26][KeyRetrieverRunner-bbb070b9-becc-4a1c-a55b-7ce96b31ed92]: getConn: mNumConns now 1

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

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

6 years ago

Metadata Update from @mharmsen:
- Issue assigned to ftweedal

6 years ago
  • Pushed to master: 33ff29c893b2e0ad13a80f59acb197a7375b7ed9
  • Pushed to ORIGIN_10_4_BRANCH: 606027b188fee6d20c17323d7c464d6630024a20

Metadata Update from @ftweedal:
- Issue close_status updated to: fixed

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4.10 (was: 0.0 NEEDS_TRIAGE)

6 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.4.8-6.fc27

6 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/2916

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