dogtagpki

#880 TPS Rewrite: Token Key Recovery
Closed: Fixed Opened by jmagne.

Closed: Fixed
Reopen Issue

Creating one ticket here for this. We currently have two types. One is a legacy method that follows scripted behavior based on the configuration. The second one is External Registration which is much more flexible and works off of instructions specifically encoded in LDAP records.

We can decide to split these if they are worked on by different developers.

This is legacy token key recovery. I would like this earlier, but July is getting crowded. Once everything basic is in place, like enrollment with server side keygen, this feature should reduce to reading config params and calling existing methods.

Proposed Milestone: 10.2.1 (per CS Meeting of 09/17/2014)

Legacy token key recovery has been done. We can have a new task for External Reg if we do not have one as of yet, for cfu.

Metadata Update from @jmagne:
- Issue assigned to cfu
- Issue set to the milestone: 10.2.1

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

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
Normal
enhancement
TPS
TPS Rewrite
Community
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.