ValidateOcspResponseInput
ValidateOcspResponseInput
Input for validateOcspResponse.
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
readonlyresponse:string|Uint8Array|ParsedOcspResponse— The OCSP response to validate.readonlyissuerCertificate:OcspCertificateSource— Certificate of the CA that issued the target certificate.readonlyrequest?:OcspRequestSource— Original request — enables nonce and request-coverage checks.readonlyresponderCertificate?:OcspCertificateSource— Explicit responder certificate — overrides embedded certificate discovery.readonlyallowChainedResponderCertificate?:boolean— Whentrue, allows delegated responder chain validation beyond direct issuance.responderRevocationPolicythen also applies to each CA certificate between the issuer and the responder.readonlytrustedOcspResponders?:readonlyOcspCertificateSource[]— 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.
readonlyresponderRevocationPolicy?:OcspResponderRevocationPolicy— Revocation policy for delegated responder certificates. Defaults to'nocheck-or-evidence'.readonlyresponderRevocationCrls?:readonlyCrlSource[]— 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).readonlyresponderRevocationCrlMaxAgeMs?:number— Maximum age of eachresponderRevocationCrlsentry'sthisUpdateatat, in milliseconds. An older CRL, or one withoutnextUpdatewhen this is unset, settles only a revocation other than certificateHold of the responder (RFC 5280 §5.3.1). Unbounded by default. ThrowsRangeErrorwhen negative or not finite.readonlyresponderRevocationUnrecognizedReasonCode?:UnrecognizedReasonCodePolicy— Treatment of aresponderRevocationCrlsentry that revokes the responder with an unrecognized CRLReason. SeeUnrecognizedReasonCodePolicy.'reject'blocks validation withresponder_revocation_unknown, even when another CRL provides good coverage. Defaults to'revoked'.readonlyresponderRevocationUnreadSupersededDeltaCrls?:SupersededDeltaCrlPolicy— Treatment ofresponderRevocationCrlsdelta CRLs that the attempt limits leave unread although one already read supersedes them. SeeSupersededDeltaCrlPolicy. Defaults to'indeterminate', which leaves the responderresponder_revocation_unknown.readonlyat?:Date— Evaluation time for freshness checks and delegated responder chain validation. Defaults tonew Date().readonlyclockSkewMs?:number— Clock-skew tolerance in milliseconds forthisUpdate/nextUpdate/producedAt, including those ofresponderRevocationCrls. It also widensresponderRevocationCrlMaxAgeMs. ThrowsRangeErrorwhen negative or not finite.readonlyprofile?:"rfc6960"|"rfc9919"— OCSP client profile to enforce. Defaults to'rfc6960', which accepts a response withoutnextUpdate(RFC 6960 §4.2.2.1).'rfc9919'applies the RFC 9919 §5 client rule and fails withnext_update_missingwhen any single response omitsnextUpdate.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 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 throwsRangeError.