03-31-2007 01:07 PM
04-04-2007 09:35 AM
04-04-2007 10:31 AM
1) How does Alfresco ensure that document approval is done by the person that submits a doc ?
2) Is there an audit trail to determine the who/when/what was done by a user in the system ?
3) Can Alfresco publish documents in restricted PDF format and therefore prevent/restrict unauthorized persons from opening it ?
4) Is there a way for alfresco to allow viewing of a document but not printing of that document, or restrict who has the ability to print vs. view a document?
5) Can alfresco replace my guard dog, my home security system and check my closet for the boogie man (this is a make or break people !!!)
04-26-2007 04:03 PM
Can a single restricted login suffice as an electronic signature?http://www.21cfrpart11.com/pages/faq/index.htm
No. The operator has to indicate intent when signing something, and he has to re-enter the user ID/password (shows awareness that he is executing a signature) and give the meaning for the e-sig. To support this, Part 11 §11.50, states that signed e-records shall contain information associated with the signing that indicates the printed name of the signer, the date/time, and the meaning, and that these items shall be included in any human readable form of the record.
04-26-2007 04:29 PM
How does the digital signature verify that the document hasn't been altered after signing?
A digital signature is computed using a set of rules and a mathematical algorithm such that the identity of the signatory and integrity of the data can be verified. Signature generation makes use of a private key to generate a digital signature. Signature verification makes use of a public key that corresponds to, but is not the same as, the private key. Each user possesses a private and public key pair. Public keys are obviously known to the public, while private keys are never shared. Anyone can verify the signature of a user by employing that user's public key. Only the possessor of the user's private key can perform signature generation. A hash function is used in the signature generation process to obtain a condensed version of data, called a message digest. The message digest is then incorporated into the mathematical algorithm to generate the digital signature. The digital signature is sent to the intended verifier along with the signed message. The verifier of the message and signature verifies the signature by using the sender's public key. The same hash function must also be used in the verification process. The hash function is specified in a separate standard.
07-13-2010 11:15 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.