Skip to content

ValidateOcspResponseInput ​

ValidateOcspResponseInput ​

Input for validateOcspResponse.

ts
interface ValidateOcspResponseInput {
	readonly response: string | Uint8Array | ParsedOcspResponse;
	readonly issuerCertificate: OcspCertificateSource;
	readonly request?: OcspRequestSource;
	readonly responderCertificate?: OcspCertificateSource;
	readonly allowChainedResponderCertificate?: boolean;
	readonly trustedOcspResponders?: readonly OcspCertificateSource[];
	readonly responderRevocationPolicy?: OcspResponderRevocationPolicy;
	readonly responderRevocationCrls?: readonly CrlSource[];
	readonly responderRevocationCrlMaxAgeMs?: number;
	readonly responderRevocationUnrecognizedReasonCode?: UnrecognizedReasonCodePolicy;
	readonly responderRevocationUnreadSupersededDeltaCrls?: SupersededDeltaCrlPolicy;
	readonly at?: Date;
	readonly clockSkewMs?: number;
	readonly profile?: "rfc6960" | "rfc9919";
	readonly signatureVerifiers?: SignatureVerifiers;
}

Properties

  • readonly response: string | Uint8Array | ParsedOcspResponse — The OCSP response to validate.

  • readonly issuerCertificate: OcspCertificateSource — Certificate of the CA that issued the target certificate.

  • readonly request?: OcspRequestSource — Original request — enables nonce and request-coverage checks.

  • readonly responderCertificate?: OcspCertificateSource — Explicit responder certificate — overrides embedded certificate discovery.

  • readonly allowChainedResponderCertificate?: boolean — When true, allows delegated responder chain validation beyond direct issuance. responderRevocationPolicy then also applies to each CA certificate between the issuer and the responder.

  • readonly trustedOcspResponders?: readonly OcspCertificateSource[] — Explicitly trusted responder certificates for this issuer's scope (RFC 6960 §4.2.2.2 criterion 1 — local responder configuration).

    A response signer matching one of these certificates is accepted without the delegated-responder issuance, chain, EKU, and revocation checks. Signature verification and responder-ID binding are still enforced. Also consulted during responder discovery when the response embeds no matching certificate.

  • readonly responderRevocationPolicy?: OcspResponderRevocationPolicy — Revocation policy for delegated responder certificates. Defaults to 'nocheck-or-evidence'.

  • readonly responderRevocationCrls?: readonly CrlSource[] — CRLs used as revocation evidence for delegated responder certificates. A delta CRL in the list updates the complete CRL it applies to (RFC 5280 §5.2.4).

  • readonly responderRevocationCrlMaxAgeMs?: number — Maximum age of each responderRevocationCrls entry's thisUpdate at at, in milliseconds. An older CRL, or one without nextUpdate when this is unset, settles only a revocation other than certificateHold of the responder (RFC 5280 §5.3.1). Unbounded by default. Throws RangeError when negative or not finite.

  • readonly responderRevocationUnrecognizedReasonCode?: UnrecognizedReasonCodePolicy — Treatment of a responderRevocationCrls entry that revokes the responder with an unrecognized CRLReason. See UnrecognizedReasonCodePolicy. 'reject' blocks validation with responder_revocation_unknown, even when another CRL provides good coverage. Defaults to 'revoked'.

  • readonly responderRevocationUnreadSupersededDeltaCrls?: SupersededDeltaCrlPolicy — Treatment of responderRevocationCrls delta CRLs that the attempt limits leave unread although one already read supersedes them. See SupersededDeltaCrlPolicy. Defaults to 'indeterminate', which leaves the responder responder_revocation_unknown.

  • readonly at?: Date — Evaluation time for freshness checks and delegated responder chain validation. Defaults to new Date().

  • readonly clockSkewMs?: number — Clock-skew tolerance in milliseconds for thisUpdate/nextUpdate/producedAt, including those of responderRevocationCrls. It also widens responderRevocationCrlMaxAgeMs. Throws RangeError when negative or not finite.

  • readonly profile?: "rfc6960" | "rfc9919" — OCSP client profile to enforce. Defaults to 'rfc6960', which accepts a response without nextUpdate (RFC 6960 §4.2.2.1). 'rfc9919' applies the RFC 9919 §5 client rule and fails with next_update_missing when any single response omits nextUpdate.

  • 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 signature would otherwise use unsupported algorithm parameters. A key that micro509 verifies natively, a key that is no OID, or a value that is no function throws RangeError.

Released under the MIT License.