VerifyPkcs7SignedDataOptions
VerifyPkcs7SignedDataOptions
Options for verifyPkcs7SignedData.
ts
interface VerifyPkcs7SignedDataOptions {
readonly expectedContentTypeOid?: string;
readonly signedAttributes?: "required" | "allowed" | "forbidden";
readonly content?: Uint8Array;
readonly signatureVerifiers?: SignatureVerifiers;
}Properties
readonlyexpectedContentTypeOid?:string— Expected eContentType OID. Defaults to id-data (1.2.840.113549.1.7.1).readonlysignedAttributes?:"required"|"allowed"|"forbidden"— Signed-attribute policy for every signer. Defaults to 'required'. 'allowed' accepts either form for id-data; 'forbidden' accepts only bare id-data signatures. RFC 5652 §5.3 always requires attributes for other types.readonlycontent?:Uint8Array— External content for a detached SignedData (RFC 5652 Section 5.2, absenteContent). Required to verify a detached signature; ignored when the SignedData embeds its own content.readonlysignatureVerifiers?:SignatureVerifiers— Caller verifiers for signature algorithms micro509 does not verify through WebCrypto, keyed by dotted-decimal signature algorithm OID. One runs only where a SignerInfo signature would otherwise use unsupported algorithm parameters, with the parameters in the signer certificate. A key that micro509 verifies natively, a key that is no OID, or a value that is no function fails withinvalid_options.