#2711 LWCA creation fails
Closed: fixed Opened by ftweedal.

Creating a LWCA fails with NPE

Error creating lightweight CA certificate: java.lang.NullPointerException
        at com.netscape.ca.CertificateAuthority.createSubCA(CertificateAuthority.java:2798)
        at com.netscape.ca.CertificateAuthority.createCA(CertificateAuthority.java:2649)
        at org.dogtagpki.server.ca.rest.AuthorityService.createCA(AuthorityService.java:186)
...
Caused by: java.lang.NullPointerException
        at com.netscape.cms.servlet.cert.EnrollmentProcessor.processEnrollment(EnrollmentProcessor.java:151)
        at com.netscape.ca.CertificateAuthority.createSubCA(CertificateAuthority.java:2762)
        ... 64 more

Metadata Update from @ftweedal:
- Issue assigned to ftweedal

Metadata Update from @ftweedal:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field keywords adjusted to regression
- 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=1452617
- Custom field type adjusted to defect
- Custom field version adjusted to ''

Pushed to master (2866f6195eb49012cf7c42089a9fbf1be819129a)

Metadata Update from @ftweedal:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue priority set to: critical
- Issue set to the milestone: 10.4.6

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: critical)

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

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

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