Michael and others, Eureka, I discovered my signing error is due to the fact that the font's are not subsetted that were used within the signature field. Apparently, even if you do not certify the document first, the making of the signature appearance having to generate font characters causes the document to be considered corrupted. Please see this article: === Check to make sure that the fonts are embedded in the underlying PDF that you imported into LiveCycle Designer. When the document is opened in Acrobat, if the fonts are not embedded, and not on the system, they will be substituted. However, in your case the PDF is rights-enabled, which disallows changes thus the error message. ... You can check the status of all your fonts under the File --> Properties --> Font tab. This will show you a listing of all fonts in the document and whether they're embedded or not. http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=1390&p=1 ===
Thus, I made a much simpler one page single form using only the courier Type 1 font and specified the courier font for all of my text and signature fields. Suddenly, iText could sign the signature field without causing the error "The Document has been altered or corrupted since the Signature was applied." Thus, this "corrupted document" mystery in my case is now solved as to cause, but I still have three more mysteries/questions that I will post as separate issues so their individual threads can be kept concise and to the point. Mike -----Original Message----- From: mkl [mailto:[email protected]] Sent: Wednesday, April 28, 2010 3:43 AM To: [email protected] Subject: Re: [iText-questions] IText Approval Signature Signing Always Reported as Corrupted Mike, M_Borg wrote: > I gave you the dictionaries because I was operating under the assumption > it might be a PDF version signing version conflict kind of thing, because > the entries are so different! There are quite a number of ways to optionally add extra information to signatures which are not required in the general case. Therefore, merely a few of those entries are interesting when checking for the cause of an approval signature being reported as corrupted; on the other hand, though, the actual signature container and the encompassing PDF (at least as the source of the signed data stream) are of major importance in such a case. Could you, thus, also upload a sample PDF demonstrating the problem? M_Borg wrote: > In answer to your question "Is there a special reason you create PKCS#1 > signatures?" - As a newbie I can only assume it must be the iText code I > am using. In that case you had better, in the long run, revamp that code to create /SubFilter/adbe.pkcs7.detached signature fields. First things first, though. M_Borg wrote: > Thus, here is my code, Your code will support the analysis of a sample PDF. Regards, Michael. -- View this message in context: http://old.nabble.com/IText-Approval-Signature-Signing-Always-Reported-as-Corrupted-tp28377946p28385745.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/ ------------------------------------------------------------------------------ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
