Headless signed revocation information

Set THPDFHeadlessCMSOptions.UseAdobeRevocationInfo to embed authenticated revocation evidence within the Adobe adbe-revocationInfoArchival signed attribute, OID 1.2.840.113583.1.1.8

Supply complete DER OCSPResponse values in RevocationEvidence.OCSPResponses or DER CertificateList values in RevocationEvidence.CRLs, and set RevocationValidation.TrustedCAFile to an explicit PEM trust store

The encoder unwraps successful basic OCSP responses into the standard BasicOCSPResponse field; callers should keep the complete OCSPResponse wrapper when preparing evidence

Signing creates the attribute before calculating the CMS signature, then authenticates the resulting signer and included timestamp chains and every evidence object prior to publishing the output

Authentication checks certificate validity, issuer relationships, OCSP responder authorisation and signatures, matching certificate identifiers, currently valid response or CRL times, revoked status and complete coverage of every non-root signer and TSA chain certificate

Every supplied evidence object must pass validation; a good response does not suppress a revoked, expired, unauthorised, malformed or unrelated object

Verification

With UseAdobeRevocationInfo enabled, HPDFVerifyHeadlessCMS and THPDFHeadlessDocument.VerifySignature read the actual signed attribute for every CMS signer

Verification reconstructs complete OCSPResponse wrappers, validates the embedded evidence and returns RevocationInfoEvaluated and RevocationInfoValid in THPDFHeadlessCMSResult

RevocationEvidence.Certificates can supply extra chain certificates during verification; its CRL and OCSP arrays are no substitute for the embedded authenticated values

Default integrity verification remains available for signatures that do not carry this attribute; enabling the profile requires the attribute and explicit evidence trust

Seed constraints and limits

A required signature seed AddRevInfo true requires this profile; required false prohibits it

The attribute is capped by MaxCMSBytes, evidence counts and validation bytes have separate RevocationValidation limits, and non-nil CMS and evidence cancellation tokens must identify the same token

Standalone HPDFBuildHeadlessRevocationInfo and HPDFReadHeadlessRevocationInfo construct and parse the bounded standard DER model; cryptographic validation occurs in the signing and verification workflows

Custom OtherRevInfo formats lie outside this profile, and this workflow fetches no network evidence and claims no historical LTA preservation