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 scep interface) put it into the batch processor - or something?


i just want to throw this questions in, before we have made up a new db design... and miss those things



greetings dalini


------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel

Reply via email to