Skip to content

VerifyPkcs7SignedDataOptions ​

VerifyPkcs7SignedDataOptions ​

Options for verifyPkcs7SignedData.

ts
interface VerifyPkcs7SignedDataOptions {
	readonly expectedContentTypeOid?: string;
	readonly signedAttributes?: "required" | "allowed" | "forbidden";
	readonly content?: Uint8Array;
	readonly signatureVerifiers?: SignatureVerifiers;
}

Properties

  • readonly expectedContentTypeOid?: string — Expected eContentType OID. Defaults to id-data (1.2.840.113549.1.7.1).
  • readonly signedAttributes?: "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.
  • readonly content?: Uint8Array — External content for a detached SignedData (RFC 5652 Section 5.2, absent eContent). Required to verify a detached signature; ignored when the SignedData embeds its own content.
  • readonly signatureVerifiers?: 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 with invalid_options.

Released under the MIT License.