dogtagpki

#2997 Token name normalization problem in pki-server subsystem-cert-validate
Closed: fixed Opened by edewata.

Closed: fixed
Reopen Issue

The pki-server subsystem-cert-validate internally calls pki client-cert-validate to validate a system certificate, and the cert token will be specified as --token parameter. However, if the token name is "Internal Key Storage Token", the command will fail with following error:

$ pki-server subsystem-cert-validate -i pki-tomcat -v ca signing
...
  Cert ID: signing
  Nickname: caSigningCert cert-pki-ca
  Usage: SSLCA
  Token: Internal Key Storage Token
Command: pki -d /var/lib/pki/pki-tomcat/alias --token Internal Key Storage Token -C /tmp/tmpfvldwj client-cert-validate Internal Key Storage Token:caSigningCert cert-pki-ca --certusage SSLCA
  Status: ERROR: ObjectNotFoundException: Certificate not found: Internal Key Storage Token:caSigningCert cert-pki-ca

Ideally the "Internal Key Storage Token" should be detected as internal token, and internal token should not be specified when calling pki client-cert-validate.

Metadata Update from @edewata:
- 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1567910
- Custom field type adjusted to None
- Custom field version adjusted to None

Metadata Update from @mharmsen:
- Issue assigned to edewata

Per 10.5.x/10.6 Triage: 10.5

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5

Metadata Update from @mharmsen:
- Issue priority set to: blocker

Fixed in master branch:

  • https://github.com/dogtagpki/pki/commit/76912e2e68fddd978be20cb92b9c76099b8bc065
  • https://github.com/dogtagpki/pki/commit/a8e7f8c80f4f6630f78990f81e4d1a06cd7f45fc

Fixed in 10.5 branch:

  • https://github.com/dogtagpki/pki/commit/d61f9729dcc102c9acbbaa8129fffb6c30fb7116

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.7 (was: 10.5)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.8 (was: 10.5.7)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.8-1.fc27

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

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
None
None
None
Lowest
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.