I’m running an approval session for a major process change next week and compliance demands a clean audit trail showin…
Open Adobe Acrobat and sign in with your administrator account.
Go to the application preferences by selecting Edit > Preferences.
Select Signatures from the list on the left.
In the Identities & Trusted Certificates section, click More.
In the Digital ID and Trusted Certificate Settings dialog, add or import your organization's trusted root certificates under Trusted Certificates.
CautionOnly import certificates from verified and authorized sources to avoid trust issues.
Set trust levels for each imported certificate by selecting it and configuring the appropriate trust options for your organization's requirements.
Close the dialog and return to the Signatures preferences pane.
Under Verification, configure the signature validation settings to enable certificate revocation checking and signature validation policies.
Configure signature validation policies by selecting options such as requiring certificate revocation checking, verifying signatures using OCSP or CRL, and validating all signatures in the document when certifying.
RecommendationEnable revocation checking to ensure signatures are still valid at the time of verification.
Click OK to save your validation policy settings.
Deploy these settings organization-wide using the Acrobat Customization Wizard or via Group Policy Objects (GPO) for managed environments.
Best practiceBLOGS suggest exporting your configured registry settings and distributing them via GPO for consistent enforcement across all user devices.
You can centrally manage trusted certificates and validation policies to ensure all users in your organization validate signatures according to your security requirements.
This runs in the Acrobat app - there is no separate API for this task.
A trusted identity is a certificate you have manually added to your Acrobat settings as reliable. It matters because Acrobat uses this list to decide if a digital signature is truly valid and from someone you trust. Without it, even a technically valid signature might show as untrusted, making it hard to confirm the signer's authenticity.
Verifying certificate information is crucial because it confirms the identity of the person or organization who signed the document. It shows details like the signer's name, the issuing authority, and the certificate's validity period. This helps you ensure that the signature is not only technically sound but also comes from a legitimate and expected source, preventing fraud or impersonation.
A 'valid' digital signature means the signature itself is technically correct, has not been tampered with, and the signer's certificate was valid at the time of signing. However, a 'trusted' signature adds another layer: it means that your Acrobat settings recognize and accept the signer's certificate as coming from a reliable source. You can have a valid signature that is not trusted by your system if you haven't explicitly added the signer's certificate to your list of trusted identities. Both are important for full assurance.