dogtagpki

#2888 certutil: could not change trust on certificate: SEC_ERROR_TOKEN_NOT_LOGGED_IN
Closed: migrated by dmoluguw. Opened by mharmsen.

Closed: migrated
Reopen Issue

Steps to Reproduce:

1. pkispawn -s CA -f ca.cfg
2. pkispawn -s KRA -f kra.cfg

Actual results:

Log file: /var/log/pki/pki-kra-spawn.20180105105230.log
Loading deployment configuration from kra.cfg.
Installing KRA into /var/lib/pki/RootKRA_hsm.
certutil: Could not find cert: NHSM6000-OCS:Server-Cert cert-RootKRA_hsm
: PR_FILE_NOT_FOUND_ERROR: File not found
Notice: Trust flag u is set automatically if the private key is present.
certutil: could not change trust on certificate: SEC_ERROR_TOKEN_NOT_LOGGED_IN: The operation failed because the PKCS#11 token is not logged in.
    ==========================================================================
                                INSTALLATION SUMMARY
    ==========================================================================
      Administrator's username:             kraadmin
      Administrator's PKCS #12 file:
            /opt/RootKRA_hsm/kraadmincert.p12
      This KRA subsystem of the 'RootKRA_hsm' instance
      has FIPS mode enabled on this operating system.
      REMINDER:  Don't forget to update the appropriate FIPS
                 algorithms in server.xml in the 'RootKRA_hsm' instance.
      To check the status of the subsystem:
            systemctl status pki-tomcatd@RootKRA_hsm.service
      To restart the subsystem:
            systemctl restart pki-tomcatd@RootKRA_hsm.service
      The URL for the subsystem is:
            https://pki.example.com:21042/kra
      PKI instances will be enabled upon system boot
    ==========================================================================

Expected results:

Not able to see any error messages.

Additional info:

This issue is occured due to certutil.
* BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1393668

This issue exists for the following two actions:
- (1) suppress this specific benign error message, and
- (2) update NSS build/runtime dependencies once this error is fixed.

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1531622

Per PKI Team Meeting of 20180118 moving to 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

Per 10.5.x/10.6 Triage: 10.5.x

edewata: misleading error message

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (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/3006

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)
Metadata
None
None
None
Normal
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.