THPDFHeadlessDocument.SetSignaturePolicyOptions

procedure SetSignaturePolicyOptions(const Options: THPDFHeadlessCMSOptions);
property SignaturePolicyOptions: THPDFHeadlessCMSOptions read FSignaturePolicyOptions;

Configure validation of existing signatures before an incremental save or a form update on a signed document

Default validation checks cryptographic integrity and the applicable ESS signing-certificate binding without requiring a CA file; provide an explicit trusted CA or timestamp policy when prior signatures must satisfy application trust requirements

The original authenticated revision controls DocMDP and FieldMDP permissions; P1 prevents field changes, while P2 and P3 allow values and appearances of existing unsigned, writable fields that are not locked

Signature dictionaries, field definitions, locked fields, page content, and protected resources retain their authenticated semantics; malformed policy syntax, invalid existing signatures, failed configured trust, and cancellation prevent the update

Use the document cancellation token for CMS and timestamp validation, keep verification budgets positive, and provide certificate and CRL paths without NUL characters

Headless document · CMS options · Signature verification

When UseAdobeRevocationInfo is enabled, every existing populated signature, including a DocTimeStamp, must authenticate its actual signed revocation attribute before a permitted form update proceeds; an unevaluated or invalid revocation report cannot authorize the update

For RFC 3161 document timestamps, signed Adobe evidence and Timestamp.RequireRevocation are separate requirements: the first authenticates the embedded signed attribute against RevocationValidation trust, while the second applies configured TSA certificate-status verification