![]() Thus, you should add revocation information and digitally time stamp the whole construct during the life time of the certificate to guarantee long term validation. The key is PdfName.M.Īs an aside, as your signing certificate is only valid for half an hour, validators may also reject it if their validation policy only trusts digital time stamps, not unsecured date-time values. But if you use a custom ExternalSignatureContainer implementation in your signing code (and not an ExternalSignature implementation), you can remove that entry in your modifySigningDictionary implementation. Unfortunately using the PdfSignatureAppearance method setSignDate to set a null value does not work, later on in the signing process this results in NullPointerException occurrence. This additionally makes your signed PDF follow the recommendation above and so be more precise. Thus, another way to resolve the issue is to make sure no signing time value is added to the signature value dictionary at all. But as the values differ, this can result in different verification results by different validators, using either one or the other value. In your case, though, the embedded signature container does contain a signingTime signed attribute with value 09:29:44 GMT which is not before the start of certificate validity.Īs that only is a recommendation, your PDF signature is not made invalid by having two signing time values. Your signature actually also violates a recommendation from the specification: The afore mentioned signing time stored in the signature field value dictionary should be used only when the time of signing is not available in the signature (the embedded signature container). You can do that by means of the PdfSignatureAppearance method setSignDate. Thus, one way to resolve the issue is to tell iText to use a time slightly (e.g. Unfortunately that is after the time iText stored as signing time in the PDF at the beginning of the signing process. At the claimed signing time, therefore, your signer certificate was not valid yet and could not create a valid signature.Īpparently you sign using a signing service that creates a short-time certificate just in time when your signature request to it arrives. Select the Signature Tool Click and drag a box onto the document where youd like to add the signature Select one of your stored signatures Click Insert. In the PDF signature field value there is a signing time 1 09:28:35 GMT but your signer certificate is valid not before 1 09:29:44 GMT and not after 1 09:59:44 GMT. That is not surprising: Your signature is not valid. Now you have a nice verified PDF which you can print without any problems.I have tried many ways to validate the signature but couldn't get any success. Now print the copy of your E-Aadhaar Card on paper and make backups of your PDF file.Sed "/mark currentfile eexec/,/cleartomark/ d" aadhaar-verified.ps | ps2pdf - aadhaar-verified.pdf The “sed” removes a stupid “copy protection” from the postscript file and ps2pdf then creates the PDF file. Print the page into the file “aadhaar-verified.ps”.Click “Close” to close the Signature Properties window.Click “OK” to close the certificate window.Click “Show Certificate” to open the certificate window.Click “Signature Properties” to open the window with the same title.Click on the question mark, a window with title “Signature Validation Status” opens.Open the file with acroread, the password is the ZIP of the city. ![]()
0 Comments
Leave a Reply. |