Hi all,
This is my scenarios:
- an user download a PDF file created by Jasper Report from system
- the user chose to open the PDF file with the reader instead of download it
before,
- the browser download it on the user temporary directory
- when the user try to save this opened PDF to an other directory a copy of
the original file was created

that is wrong on my scenario because system had recorded the HASH of the
original PDF document on downloading

To prevent this PDF-copy creation on save I adopt this workaround:

<pd4ml:permissions password="empty" strongEncryption="false"
rights="34820"/>

Now I have a new requirement, the user should be able to sign this PDF. 
Unfortunately the document so created is unmodifiable and all other tried
rights configurations except then rights="34820" lose the
prevent-PDF-copy-on-save feature.

My question is:
exists some kind of rights configuration that maintains the
prevent-PDF-copy-on-save feature but permit to sign the PDF document?

Thanks in advance,
Andrea



--
View this message in context: 
http://itext.2136553.n4.nabble.com/sign-a-prtected-PDF-tp4660802.html
Sent from the iText mailing list archive at Nabble.com.

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions

iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference 
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples: 
http://itextpdf.com/themes/keywords.php

Reply via email to