Hi
within the bp there is a function "postproc_cert" defined which triggers if the state
is "enrolled_cert". In the normal workflow there is no state "enrolled_cert" neither is
there a bp/lib/postproc_cert.sub.
What it is this good for? Did I miss something?
I planned the following state transition (with enrolled_):
pin --> pkcs12 --> cert --> postproc_cert
First enroll the PIN. Second rollout of the PKCS#12 (or better key and cert) to the user. Finally rollout of the cert (to the infrastructure). After the last step we can do something with the cert. Therefore we planned postproc cert. You can place it for example in a newsletter. enroll_cert is focussed on OpenCA and postproc_cert is focussed on the customer.
More or less when we finished enroll_pkcs12 and then there was some silence around. Perhaps Oli knows what the actual plan is.
Michael -- ------------------------------------------------------------------- Michael Bell Email: [EMAIL PROTECTED] ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482 (Computing Centre) Fax: +49 (0)30-2093 2704 Humboldt-University of Berlin Unter den Linden 6 10099 Berlin Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
