PKI console does not display CA signing certificate in case of shared tomcat

[pki-bot]

This issue was migrated from Pagure Issue #1505. Originally filed by aakkiang (@aakkiang) on 2015-07-20 18:46:57:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1244749

---

PKI console does not display CA signing certificate in case of shared tomcat.

Steps to Reproduce:

Login to KRA subsystem console as admin user
Select the Configuration tab.
Click on "System Keys and Certificates" in the left navigation menu.

Actual results:

CA certificates tab does not display CA signing cert info.

Expected results:

CA certificates tab should display CA signing cert info.

Additional info:

# certutil -L -d /var/lib/pki/pki-master/kra/alias

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

casigningcert                                                CTu,Cu,Cu
Server-Cert cert-pki-RootCA                                  u,u,u
caauditsigningcert                                           u,u,Pu
kra3transportcert                                            u,u,u
kra3auditsigningcert                                         u,u,Pu
ocsp3auditsigningcert                                        u,u,Pu
tps1auditsigningcert                                         u,u,Pu
caocspsigningcert                                            u,u,u
casubsystemcert                                              u,u,u
kra3storagecert                                              u,u,u
ocsp3signingcert                                             CTu,Cu,Cu
tks1auditsigningcert                                         u,u,Pu

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-07-28 01:15:00

Per CS/DS Meeting of 07/27/2015: 10.3

[pki-bot]

Comment from rpattath (@rpattath) at 2015-08-19 16:39:55

I do not see the caSigning cert under CA Certificates tab in CA console.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-06-24 04:34:44

Per PKI Bug Council of 06/23/2016: 10.4

[pki-bot]

Comment from aakkiang (@aakkiang) at 2017-02-27 14:08:40

Metadata Update from @aakkiang:

• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-03-03 19:03:30

Metadata Update from @mharmsen:

• Custom field feature adjusted to ''
• Custom field proposedmilestone adjusted to ''
• Custom field proposedpriority adjusted to ''
• Custom field reviewer adjusted to ''
• Custom field version adjusted to ''
• Issue close_status updated to: None
• Issue set to the milestone: 10.4 (was: UNTRIAGED)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:43:33

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:43:33

Metadata Update from @mharmsen:

• Issue set to the milestone: FUTURE (was: 10.4)