--
You received this message because you are subscribed to the Google Groups "Adobe LiveCycle Developers" group.
To post to this group, send email to live...@googlegroups.com.
To unsubscribe from this group, send email to livecycle+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/livecycle?hl=en.
1. Use check sum algorithm to verify the status of secured fields. The
check sum will be calculated on the server as soon as the form is
created, and the check sum value will be bound the form and also saved
on the server. Everytime the form is submitted, I will recalculate the
checksum and confirm if it was changed.
=> I think this will help.. but applying check sum for an individual field will not be of worth.. though i would like your share such implementations with all of us.
2. Using Adobe LiveCycle ES Digital Signature Services. As soon as the
form is created, I will only the Fields to be secured. Since I am
using ASP.NET, then I have to use Web Services to Generate the PDF and
sign the Fields to be secured.
=> if you are pulling data from Back-End System automatically may be using web service then i think protected fields will be changed at the initialization script and thus the Digital Signature can be tampered by itself.
Also to my knowledge we shouldn't put signatures on the forms which have initialization script or Dynamic forms as it can tamper documents easily.
Based on your requirement i have created a sample PDF form wherein i have disabled the Export data Tab.
Kindly try exporting data from the attached sample PDF.
Again if you tamper it then we can think further on it.. but if you cannot then you can use this as one of the solution to consider.. :)
Regards,
Hemant Garg.