After applying your code for getCrlUrlFromExtensionValue instead of mine (I'm using BC v1.60), I have tried to sign the document with qualified signature (from PKS CA) and with recognized TimeStampAuthority (also from PKS CA).
Now adding LTV information finishes without errors, and Adobe Acrobat Reader shows "Signature is LTV enabled". For my particular case, that is perfectly good - thank you so much for your help! I have used FreeTSA only for testing purposes, so regarding my case it's not crucial to make code work with it. However, since it is a well known and free TSA, it might be good idea to check how the code behaves. Thank you again and best regards, Predrag -----Original Message----- From: Tilman Hausherr [mailto:thaush...@t-online.de] Sent: Thursday, November 14, 2019 8:49 PM To: users@pdfbox.apache.org Subject: Re: After adding validation information, Adobe Reader says Signature is not LTV enabled Am 14.11.2019 um 08:26 schrieb Tilman Hausherr: > I will work on this topic again tonight, hopefully. Current status: I found out why the OCSP problem didn't happen, this is because of a problem with recent BC versions. I changed that and now I hit the OCSP error, and it recovers. and uses CRL instead. How I have 15 certificates in the DSS, while you have 12. For your original signed file, Adobe mentions that there is a timestamp, but that this timestamp wasn't verified. My next step will be to sign and timestamp and validate a file with freetsa to see if this works. (this weekend, hopefully) Tilman --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@pdfbox.apache.org For additional commands, e-mail: users-h...@pdfbox.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@pdfbox.apache.org For additional commands, e-mail: users-h...@pdfbox.apache.org
