ValidateCertificateRevocationListInput
ValidateCertificateRevocationListInput
Input for validateCertificateRevocationList.
ts
interface ValidateCertificateRevocationListInput {
readonly crl: CrlSource;
readonly issuerCertificate: CrlCertificateSource;
readonly at?: Date;
readonly clockSkewMs?: number;
readonly maxAgeMs?: number;
readonly signatureVerifiers?: SignatureVerifiers;
}Properties
readonlycrl:CrlSource— The CRL to validate.readonlyissuerCertificate:CrlCertificateSource— Certificate of the CA that should have signed the CRL.readonlyat?:Date— Evaluation time for freshness checks. Defaults tonew Date().readonlyclockSkewMs?:number— Tolerance in milliseconds for clock skew when checkingthisUpdateandnextUpdate. It also widensmaxAgeMsby the same amount. ThrowsRangeErrorwhen negative or not finite.readonlymaxAgeMs?:number— Maximum age ofthisUpdateatat, in milliseconds. A CRL older than this fails withstale_crleven whennextUpdateis absent or later. Unbounded by default, in which case a CRL withoutnextUpdatefails withstale_crl. RFC 5280 §3.3 leaves the required recency of revocation data to local policy.checkCertificateRevocationAgainstCrlstill reports a revocation such a CRL lists with a reason other than certificateHold, for a certificate that has not expired (RFC 5280 §5.3.1).readonlysignatureVerifiers?:SignatureVerifiers— Caller verifiers for signature algorithms micro509 does not verify through WebCrypto, keyed by dotted-decimal signature algorithm OID. One runs only where the CRL signature would otherwise use unsupported algorithm parameters, with the parameters in the issuer certificate. A key that micro509 verifies natively, a key that is no OID, or a value that is no function throwsRangeError.