Hi dalini,
oh, just as we talking about database desing in relation to sign actions and state changes:
do we have an option to create request objects, which just have a dn and a pwd (pre shared secret) stored? (which also may have been signed, means pre approved by 1:n operators?)
this is necessary for autmated processing (for example of scep requests ;)...
that means: if a pkcs#10 request gets inserted, and the system may find a prepared request with the same dn and the same pre shared secret, this request should get to the state 'approved' automagically ;) and so can be handled in the backend...
i'm not quite sure, how the batchprocessor right now gets its input ;)
may it be necessary for customer workflow definitions to mark such things special? so the system knows - preapproved (request comes through
Hmm, latest plans will merge batch-system into the normal workflow, so both concepts are mixed in the future - perhaps should we use the new extended data tables (that come from the batch) for saving such a preshared secret or even the Token Requests, which are a similar problem...
Michael: What do ypu think about,
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
