Per CS/DS meeting of 03/31/2014 - 10.2 April.

Part 1 checkin:

commit 002e2625e187398b4100ab41ac43eec4b8c1cf5f
Author: Christina Fu cfu@redhat.com
Date: Wed Jun 11 18:15:06 2014 -0700

ticket #941 Part1 TPS Rewrite: Enrollment, Recovery, KeyRecovery, revoke/unr

This patch is the 1st patch to ticket #941 - TPS Rewrite: Enrollment, Recovery, KeyRecovery, revoke/unrevoke processor

It mainly allows tomcat TPS to
1. take the raw bytes of public key generated on the token,
2. parse it and transform it into a PublicKey structure
3. send request to CA
4. upon success of the issuance from CA, receive and decode into X509CertImp ready to be processed and injected to the token
5 takes token profile (tokenKey) from CS.cfg for the remote handlers

It currently does not:

• handle ECC
• verify the key proof (challenge)

This is the 3rd cut of the policy code plus renewal code (up to the point it gets renewed cert from CA), plus the retrieveCertificate code needed for recovery.
The is a "pre-agreed" code to merge with Jack to speed up the dev as well as providing parts of the code he needs. More testing/polishing to come;

commit 0713dc5e2060cf02a954a15b1252d5b2124bfc34
Author: Christina Fu cfu@redhat.com
Date: Wed Aug 27 17:32:48 2014 -0700

ticket 941 Renewal/Reenroll/Recovery/Renew policy 3rd cut; Renewal code; Ret

commit 82d3ed74289857b5fa60a842979406a2a8acecda
Author: Christina Fu cfu@redhat.com
Date: Tue Sep 2 20:30:42 2014 -0700

ticket #941 Rest interface triggered revoke/unrevoke and cert status update; Recovery

commit 99e6330ce13e55ac325d76bdc33f1b1b00cba5d3
Author: Jack Magne jmagne@dhcp-16-213.sjc.redhat.com
Date: Wed Aug 20 11:43:56 2014 -0700

Recovery and Renewal feature:
1. Basic token key recovery functionality is there.
2. Tested with mostly the "damaged" scenerio. The low level
code that writes the recovered certs to the token works and has been
tested with a real token. Some of the other more obscure cases need
some more testing, for instance, the temporary on hold scenario.
3. Renewal has been tested with a real token to work.
4. Much of the complex code to write cert objects and key objects,
as well as importing recovered keys, has been centralized to a method.
This leaves the calling code simpler and easier to trouble shoot.
5. Added a method to check token operation transition states.
6. Fixed an issue with formatting a blank token I introduced.
7. Fixed a few issues with updating certificate records for a token that were discovered.
8. Added tps code to retrieve a certificate for the recovery case.
9. Minor Review fixes.

Code to actually recover certs and keys onto a real token.

This concludes the initial "TPS rewrite" work from cfu & jmagne.

More testing and polishing will follow in the following releases with individual tickets specific to each improvement.

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

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.