How to Fix Invalid Policy Constraint for Sectigo Certificates in PDF
Question details
Users encounter an invalid policy constraint error when opening a digitally signed PDF that uses a Sectigo certificate.

- Product
- Adobe Acrobat / PDF
- Device & OS
- not provided
- Scenario
- Verifying digital signatures on a PDF document signed with a Sectigo certificate.
- Observed behavior
- The PDF software marks the signature as invalid and reports an invalid policy constraint because the Certificate Policies extension does not meet Adobe Approved Trust List (AATL) requirements.
Ensure you have access to the Certificate Viewer in your PDF software to inspect the advanced properties and extensions of the digital signature.
Inspect and Verify Certificate Policies in the Certificate Viewer
Use the built-in Certificate Viewer to compare the signing certificate's policy OID against permitted AATL policies.
This issue is typically caused by a policy restriction rather than a Key Usage or Extended Key Usage problem. When a certification authority is added to the Adobe Approved Trust List (AATL), end-entity certificates are required to comply with specific policy constraints. If these policies are missing, the signature cannot establish trust.
Click on the digital signature in your PDF document to open the Signature Properties, then click to view the signer's certificate.
Select the top issuing certificate in the Certificate Viewer hierarchy. Navigate to the Policies tab to see the list of permitted policies.
Select your specific signing certificate from the tree. Open the Details tab and locate the Certificate Policies extension.
Verify if your certificate's policy OID matches one of the permitted policies. If the required policy OID is missing, you must contact Sectigo to obtain a compliant certificate.

View and Manage PDF Digital Signatures with WPS Office
WPS Office includes a robust PDF editor that allows you to easily view, manage, and validate digital signatures. With high compatibility and advanced security features, handling signed documents is seamless.
- 1. Open the signed PDF: Launch WPS Office and open your digitally signed PDF document.
- 2. Access signature details: Navigate to the Protect tab and select Manage Signatures, or click directly on the signature field in the document.
- 3. Validate the signature: Review the signature properties and certificate details to verify the authenticity and trust status of the document.

Frequently Asked Questions
What does 'invalid policy constraint' mean for PDF signatures?
It means the digital certificate used to sign the PDF lacks the specific Certificate Policies extension required by the Adobe Approved Trust List (AATL), preventing the software from verifying trust.
Is an invalid policy constraint related to Key Usage errors?
No, this is specifically a policy restriction issue. It is not caused by incorrect Key Usage or Extended Key Usage parameters in the certificate.
How do I fix a missing policy OID in my digital certificate?
You need to contact your certificate issuer (such as Sectigo) and request that they issue or reissue your certificate with the proper AATL-compliant Certificate Policies extension included.
Why does my Sectigo signature show as invalid instead of unknown?
Some PDF readers currently categorize a failure to establish policy trust as an 'invalid signature'. Software developers plan to update this behavior in the future so that unverified policy constraints correctly display the signature as 'unknown'.




