#1505 PKI console does not display CA signing certificate in case of shared tomcat
Closed: migrated 3 years ago by dmoluguw. Opened 8 years ago by aakkiang.

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

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

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

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

Metadata Update from @aakkiang:
- Issue set to the milestone: UNTRIAGED

7 years ago

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)

7 years ago

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

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata