RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1616134 - Unable to install with admin-generated keys
Summary: Unable to install with admin-generated keys
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.5
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks: 1656297
TreeView+ depends on / blocked
 
Reported: 2018-08-15 03:25 UTC by Asha Akkiangady
Modified: 2020-10-04 21:45 UTC (History)
7 users (show)

Fixed In Version: pki-core-10.5.16-2.el7
Doc Type: Enhancement
Doc Text:
.The `pkispawn` utility now supports using keys created in the NSS database during CA, KRA, and OCSP installations Previously, during a Certificate System installation, the pkispawn utility only supported creating new keys and importing existing keys for system certificates. With this enhancement, pkispawn now supports using keys the administrator generates directly in the NSS database during certificate authority (CA), key recovery authority (KRA), and online certificate status protocol (OCSP) installations.
Clone Of:
: 1656297 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:07:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 3171 0 None closed Mechanism to install with custom keys 2020-10-30 11:07:06 UTC
Red Hat Product Errata RHBA-2019:2228 0 None None None 2019-08-06 13:07:49 UTC

Description Asha Akkiangady 2018-08-15 03:25:38 UTC 
Description of problem:
OCSP pkispawn installation with admin-generated keys instead of pkispawn-generated keys throws null pointer exception. 

Version-Release number of selected component (if applicable):
pki-server-10.5.1-15.el7_5.noarch

How reproducible:
Always

Steps to Reproduce:
The issue is reproducible in both ECC and RSA installations.
1. Install RootCA. Create a CMC SharedToken.
2. Install OCSP step 1 without generating csr. 
3. Generate csr using PKCS10Client command.  Use CMCShared token method to generate certificates. 
4. Configure pkispawn file with csr and cert files generated in step 3 and run OCSP pkispawn step 2. 


Actual results:
pkispawn fails with following error:

pkispawn    : DEBUG    ........... <?xml version="1.0" encoding="UTF-8" standalone="no"?><XMLResponse><State>0</State><Type>OCSP</Type><Status>running</Status><Version>10.5.1-14.el7_5</Version></XMLResponse>
pkispawn    : INFO     ....... constructing PKI configuration data.
pki.nssdb   : DEBUG    Command: certutil -L -d /opt/pki-ECC-masterOCSP/ocsp/alias -f /tmp/tmpzcBIlw/password.txt -n PKI OCSP Administrator for ECC-Non-TMS-OCSP -a
pkispawn    : INFO     ....... configuring PKI configuration data.

Installation failed:
<html><head><title>Apache Tomcat/7.0.76 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 500 - java.lang.NullPointerException</h1><HR size="1" noshade="noshade"><p><b>type</b> Exception report</p><p><b>message</b> <u>java.lang.NullPointerException</u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
	org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76)
	org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212)
	org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:149)
	org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:372)
	org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
	org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
	org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:498)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:288)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:285)
	java.security.AccessController.doPrivileged(Native Method)
	javax.security.auth.Subject.doAsPrivileged(Subject.java:549)
	org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:320)
	org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:175)
	java.security.AccessController.doPrivileged(Native Method)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:498)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:288)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:285)
	java.security.AccessController.doPrivileged(Native Method)
	javax.security.auth.Subject.doAsPrivileged(Subject.java:549)
	org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:320)
	org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:260)
</pre></p><p><b>root cause</b> <pre>java.lang.NullPointerException
	org.mozilla.jss.util.Base64OutputStream.write(Base64OutputStream.java:86)
	com.netscape.cmsutil.crypto.CryptoUtil.base64Encode(CryptoUtil.java:1074)
	org.dogtagpki.server.rest.SystemConfigService.processCert(SystemConfigService.java:443)
	org.dogtagpki.server.rest.SystemConfigService.processCerts(SystemConfigService.java:303)
	org.dogtagpki.server.rest.SystemConfigService.configure(SystemConfigService.java:166)
	org.dogtagpki.server.rest.SystemConfigService.configure(SystemConfigService.java:101)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:498)
	org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137)
	org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:280)
	org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234)
	org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221)
	org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
	org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179)
	org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220)
	org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:498)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:288)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:285)
	java.security.AccessController.doPrivileged(Native Method)
	javax.security.auth.Subject.doAsPrivileged(Subject.java:549)
	org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:320)
	org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:175)
	java.security.AccessController.doPrivileged(Native Method)
	org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:498)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:288)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:285)
	java.security.AccessController.doPrivileged(Native Method)
	javax.security.auth.Subject.doAsPrivileged(Subject.java:549)
	org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:320)
	org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:260)
</pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/7.0.76 logs.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.76</h3></body></html>

Please check the OCSP logs in /var/log/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/ocsp.

=============================================================
OSCP debug log has this:
14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: autoShutdown crumb file path? /var/lib/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/logs/autoShutdown.crumb
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: about to look for cert for auto-shutdown support:auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: cert not found:auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: Exception:org.mozilla.jss.crypto.ObjectNotFoundException: Certificate not found: auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: done init id=debug
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: initialized debug
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: initSubsystem id=log
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: ready to init id=log
[14/Aug/2018:11:22:00][localhost-startStop-1]: Event filters:
[14/Aug/2018:11:22:00][localhost-startStop-1]:  - RANDOM_GENERATION: (Outcome=Failure)
[14/Aug/2018:11:22:00][localhost-startStop-1]:  - SELFTESTS_EXECUTION: (Outcome=Failure)
[14/Aug/2018:11:22:00][localhost-startStop-1]: Creating RollingLogFile(/var/lib/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/logs/ocsp/signedAudit/ocsp_cert-ocsp_audit)
[14/Aug/2018:11:22:00][localhost-startStop-1]: Event filters:
[14/Aug/2018:11:22:00][localhost-startStop-1]: Creating RollingLogFile(/var/lib/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/logs/ocsp/system)
[14/Aug/2018:11:22:00][localhost-startStop-1]: Event filters:
[14/Aug/2018:11:22:00][localhost-startStop-1]: Creating RollingLogFile(/var/lib/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/logs/ocsp/transactions)
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: restart at autoShutdown? false
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: autoShutdown crumb file path? /var/lib/pki/rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11/logs/autoShutdown.crumb
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: about to look for cert for auto-shutdown support:auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: cert not found:auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
[14/Aug/2018:11:22:00][localhost-startStop-1]: CMSEngine: Exception:org.mozilla.jss.crypto.ObjectNotFoundException: Certificate not found: auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11
==================================================
OCSP's db has audit signing cert imported with correct nickname that was given in pkispawn config "ocsp_audit_signing_ecc_nontms_aakkiang-nocp11":

# certutil -L -d .

Certificate Nickname                                         Trust Attributes
                                                             SSL,S/MIME,JAR/XPI

ocsp_audit_signing_ecc_nontms_aakkiang-nocp11                ,,P  
ocsp_sslserver_ecc_nontms_aakkiang-nocp11                    CTu,Cu,Cu
CA Signing Certificate - Example-rhcs93-ECC-CA               CT,C,C
caSigningCert-ECC-NonTMS-SubCA-aakkiang-nocp11               CT,C,C
===================================================

The problem could be that pkispawn was run with "ocsp_audit_signing_ecc_nontms_aakkiang-nocp11" in the config, but the server was looking for "auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11" instead.

Expected results:
pkispawn of OCSP should succeed. 

Additional info:
A possible workaround that QE can try: running pkispawn with a nickname that matches the one it's looking for, i.e. "auditSigningCert cert-rhcs93-ECC-NonTMS-OCSP-aakkiang-nocp11".

Note: The problem probably happens on all subsystems too, not just ocsp.
Comment 3 Endi Sukma Dewata 2018-08-29 13:24:43 UTC 
The patches are available here:
https://github.com/dogtagpki/pki/pull/37

A COPR build is available here:
https://copr.devel.redhat.com/coprs/edewata/pki-10.5/build/22038/

The documentation is available here:
http://www.dogtagpki.org/wiki/Installing_OCSP_with_Custom_Keys
Comment 4 Endi Sukma Dewata 2018-11-13 20:51:43 UTC 
Fixed in 10.5 branch:
* https://github.com/dogtagpki/pki/commit/8bf25507886c446594fa1bd82e3040ab79b271b3
* https://github.com/dogtagpki/pki/commit/f3dc6c79370d8b57362272c40bd9f67aaf791710
* https://github.com/dogtagpki/pki/commit/88271a9b3d829669fb997ee6158081da18faed97
* https://github.com/dogtagpki/pki/commit/e50f3b0b6034c2c18a0775f2e91fd2e5ea21678f
* https://github.com/dogtagpki/pki/commit/9cef57869f01e89653331c0e22c9d3bacf7744ce
* https://github.com/dogtagpki/pki/commit/80defb1b7602eb59f5ee817a76acac86490ce853
* https://github.com/dogtagpki/pki/commit/9a984ee0a709645fe9b6044367ed28076692ee86
* https://github.com/dogtagpki/pki/commit/eb8baf8b51e3c897caddbc16df2fd226308a0876
* https://github.com/dogtagpki/pki/commit/a8405a1f8bd4c3fd10213725a32da0419e622252
Comment 5 Endi Sukma Dewata 2018-11-13 20:54:24 UTC 
Supported scenarios:
* https://github.com/dogtagpki/pki/blob/DOGTAG_10_5_BRANCH/docs/installation/Installing_CA_with_Custom_CA_Signing_Key.md
* https://github.com/dogtagpki/pki/blob/DOGTAG_10_5_BRANCH/docs/installation/Installing_KRA_with_Custom_Keys.md
* https://github.com/dogtagpki/pki/blob/DOGTAG_10_5_BRANCH/docs/installation/Installing_OCSP_with_Custom_Keys.md
Comment 11 errata-xmlrpc 2019-08-06 13:07:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2228
Note You need to log in before you can comment on or make changes to this bug.