added
Directory URLs for Google ACME providerfixed
Invalidate ACME provider directory cache after 24 hoursfixed
Retry HTTP requests on server errors or when rate limited - #89
fixed
Allowclient.auto()
being called with an empty CSR common namefixed
Bug when callingupdateAccountKey()
with external account binding
added
Support and tests for satisfyingtls-alpn-01
challengeschanged
Replacejsrsasign
with@peculiar/x509
for certificate and CSR handlingchanged
MethodgetChallengeKeyAuthorization()
now returns$token.$thumbprint
when called with atls-alpn-01
challenge- Previously returned base64url encoded SHA256 digest of
$token.$thumbprint
erroneously - This change is not considered breaking since the previous behavior was incorrect
- Previously returned base64url encoded SHA256 digest of
fixed
Allow self-signed or invalid certs when validatinghttp-01
challenges that redirect to HTTPS - #65fixed
Wait for all challenge promises to settle before rejectingclient.auto()
- #75
fixed
Upgrade[email protected]
- GHSA-rh63-9qcf-83gffixed
Upgrade[email protected]
- CVE-2023-45857
- Upgrade guide here
added
New native crypto interface, ECC/ECDSA supportbreaking
Remove support for Node v10, v12 and v14breaking
Prioritize issuer closest to root during preferred chain selection - #46changed
Replacebluebird
dependency with native promise APIschanged
Replacebacko2
dependency with internal utility
fixed
Upgrade[email protected]
fixed
Upgrade[email protected]
- CVE-2022-24771, CVE-2022-24772, CVE-2022-24773
fixed
Use SHA-256 when signing CSRs
backport
Use SHA-256 when signing CSRs
added
Directory URLs for ACME providers Buypass and ZeroSSLfixed
Skip already valid authorizations when usingclient.auto()
fixed
Upgrade[email protected]
fixed
ZeroSSLduplicate_domains_in_array
error when usingclient.auto()
added
Support for external account binding - RFC 8555 Section 7.3.4added
Ability to pass through custom logger functionchanged
Increase defaultbackoffAttempts
to 10fixed
Deactivate authorizations where challenges can not be completedfixed
Attempt authoritative name servers when verifyingdns-01
challengesfixed
Error verbosity when failing to read ACME directoryfixed
Correctly recognizeready
andprocessing
states - RFC 8555 Section 7.1.6
fixed
Upgrade[email protected]
- CVE-2021-3749
fixed
Upgrade[email protected]
- CVE-2020-28168
fixed
Bug when encoding PEM payloads, potentially causing malformed requests
fixed
Missing TypeScript definitions
added
OptionpreferredChain
added toclient.getCertificate()
andclient.auto()
to indicate which certificate chain is preferred if a CA offers multipleadded
Methodclient.getOrder()
to refresh order from CAfixed
Upgrade[email protected]
fixed
Error when attempting to revoke a certificate chainfixed
Missing URL augmentation inclient.finalizeOrder()
andclient.deactivateAuthorization()
fixed
Add certificate issuer to response fromforge.readCertificateInfo()
fixed
Explicitly set defaultaxios
HTTP adapter - axios/axios#1180
fixed
Upgrade[email protected]
- CVE-2020-7720
breaking
Remove support for Node v8breaking
Remove deprecatedopenssl
crypto modulefixed
Incorrect TypeScriptCertificateInfo
definitionsfixed
Allow trailing whitespace character inhttp-01
challenge response
fixed
Improvements to TypeScript definitions
added
TypeScript definitionsfixed
Allow missing ACME directory meta field - RFC 8555 Section 7.1.1
added
New optionskipChallengeVerification
added toclient.auto()
to bypass internal challenge verification
added
More extensive testing using letsencrypt/pebblechanged
When creating a CSR,commonName
no longer defaults to'localhost'
- This change is not considered breaking since
commonName: 'localhost'
will result in an error when ordering a certificate
- This change is not considered breaking since
fixed
Retry signed API requests onurn:ietf:params:acme:error:badNonce
- RFC 8555 Section 6.5fixed
Minor bugs related toPOST-as-GET
when callingupdateAccount()
fixed
Ensure subject common name is present in SAN when creating a CSR - CAB v1.2.3 Section 9.2.2fixed
Send empty JSON body when responding to challenges - RFC 8555 Section 7.5.1
backport
Minor bugs related toPOST-as-GET
when callingclient.updateAccount()
backport
Send empty JSON body when responding to challenges
added
UTF-8 support when generating a CSR subject using forge - RFC 5280fixed
ImplementPOST-as-GET
for all ACME API requests - RFC 8555 Section 6.3
backport
ImplementPOST-as-GET
for all ACME API requests
added
Exposeaxios
instance to allow manipulating HTTP client defaultsbreaking
Remove support for Node v4 and v6breaking
Remove Babel transpilation
added
DNS CNAME detection when verifyingdns-01
challenges
added
Support fortls-alpn-01
challenge key authorization
fixed
Handle and throw errors from OpenSSL process
added
New node-forge crypto interface, removes OpenSSL CLI dependencyadded
Support nativecrypto.generateKeyPair()
API when generating key pairs
added
Ability to set and get current account URLfixed
Replace HTTP clientrequest
withaxios
fixed
Auto-mode no longer tries to create account when account URL exists
fixed
Key rollover in compliance with draft-ietf-acme-13
breaking
ACMEv2breaking
API changesbreaking
Rewrite to ES6breaking
Promises instead of callbacks
- API stable
fixed
Bug causing invalid anti-replay nonce
breaking
OpenSSL methodreadCsrDomains
andreadCertificateInfo
now return domains as an objectfixed
Added and fixed some tests
acme-client
released