Hello Pierre,
But I still do not understand the process the RA Operator should follow. Do you mean that once the RA operator received a token request (no crypto stuff involved) and approve it, he will start a complete process from scratch on his own requesting a Certificate from the Pub interface? What are the steps then?
Ergh - AFAIK Michael used this to trigger a batch-process - so the "normal" Webfrontend is no longer used - but I never dealt with this....
Also, could you confirm me that the token.xml has to be edited only when you want a token or HSM to manage the certificates signatures of the CA(i.e. the CA private key will be on the token/HSM)
Yes thats right - token.xml is only for configuring the crypto backend
NB. I noticed a little bug in the token.xml.in file for the opensc section: line 369 <value>@var_prefix@/var/crypto/chain</value>should be <value>@var_prefix@/crypto/chain</value>
ok I see - I will fix it Oliver -- Diese Nachricht wurde digital unterschrieben oliwel's public key: http://www.oliwel.de/oliwel.crt Basiszertifikat: http://www.ldv.ei.tum.de/page72
smime.p7s
Description: S/MIME Cryptographic Signature
