dogtagpki

Clone
Source Code
GIT

#1146 Tomcat TPS: missing "keyType" for renewed certs in the cert records
Closed: Fixed None Opened 9 years ago by cfu.

Closed: Fixed
Reopen Issue

It appears that the cert records of the newly renewed certs are missing the "keyType" attribute.

To exercise renewal:

  • Add 4:4 to the following in CS.cfg, like
    tps.operations.allowedTransitions=0:0,0:4,4:0,4:4
  • enroll a token against an existing profile, such as userKey
  • go on TPS admin UI to see the certs on the token
  • enroll the exact same token again
  • observe the cert records for the newly renewed certs appear in the tokendb.

Notice that the "key type" of the cert records are missing data

forgot to mention one step:

  • before enrolling the exact token again, go to TPS admin UI and add the following policy to the policy field of the token:

RENEW=YES

commit 3a40420a042db5f577a5a17c8a49ccd1d1d73955
Author: Christina Fu cfu@redhat.com
Date: Thu Sep 4 17:01:34 2014 -0700

Ticket #1146 Tomcat TPS: missing "keyType" for renewed certs in the cert rec

Metadata Update from @cfu:
- Issue set to the milestone: 10.2 - 08/14 (August)
7 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/1709

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.

Login to comment on this ticket.

Metadata
None
None
None
None
major
None
None
None
defect
None
None
None
None
TPS Rewrite
Community
None
None
None
None
None
None
TPS
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.