While trying to install CA interactively, the admin certificate is missing from the client NSS database.
The following error occurs:
[root@localhost /]# pki -d ~/.dogtag/pki-tomcat/ca/alias client-cert-find SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. --------------------- No certificates found --------------------- [root@localhost /]# certutil -L -d ~/.dogtag/pki-tomcat/ca/alias Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1458015 - Issue priority set to: critical - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @edewata: - Issue priority set to: major (was: critical)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Is this still a problem? Or due to the dependency issues alluded to by the error messages above?
Does the PK12 with the admin cert exist?
Ae you sure that the client certdb actually exists? Its likely to have been removed because pki_client_database_purge=True
I'm not sure this is a real bug in that case.
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Insufficient data exists to reproduce this issue
Metadata Update from @mharmsen: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6.0 (was: 10.6)
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/2835
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.