![]() To test, I booted up a VM with Win7 and Acrobat Standard 9 (9.5.5) and was able to reproduce the issue. ![]() When I asked which version of Acrobat they are using, he replied that they have Acrobat 9. We've followed the Adobe guidelines for applying certificate based signatures ( ) and have not had a problem until recently when a client reported that the signatures are coming up invalid. Each document has multiple signatures, the first of which is the certifying signature, then the others are approval signatures. We use Acrobat Standard 11 to digitally sign documents using Adobe Certified Document Services (CDS) certificates issued by GlobalSign. I've attempted to contact Adobe support about this issue, but they referred me here because the issue is with a previous version of Acrobat. I'm aware that un-checking the "Require certificate revocation checking to succeed whenever possible during signature verification" solves the issue (as it simply skips the CRL checking), so I prefer to have the CRL check working Is it a known bug/limitation? will it be fixed? is there a way to allow/force Adobe to read the LDAP url? I should mention that when I use a certificate with a CDP entry that points to an HTTP url, I don't get such errors. Location: ldap:///CN=ROOT,CN=CDP,CN=Public Key Services,CN=Services,CN=Configuration,DC=TEST,DC=LOCAL?certificateRev ocationList?base?objectclass=cRLDistributionPointĬannot connect to server._ The CRL of the certificate is pointed by an LDAP url (ldap:///CN=ROOT,CN=CDP,CN=Public Key Services,CN=Services,CN=Configuration,DC=TEST,DC=LOCAL?certificateRev ocationList?base?objectclass=cRLDistributionPoint).
0 Comments
Leave a Reply. |