We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
this is a feature request for:
Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension https://www.ietf.org/archive/id/draft-ietf-acme-ari-02.html
This extension allows CA's to inform the ACME client that a renewal is necessary earlier than normal for example due to an upcoming mass revocation:
For example, a CA could suggest that clients renew prior to a mass-revocation event to mitigate the impact of the revocation
For example this would cover various mass revocation events like: #4936
The alternative is that CA's need to email their users, which then have to --renew --force the affected certs.
--renew --force
Current status in other projects:
I believe this would be a good addition to the client.
Lukas
The text was updated successfully, but these errors were encountered:
As a note, ACME Renewal Information (ARI) has entered Last Call. I would encourage acme.sh to consider implementing ARI.
acme.sh
Sorry, something went wrong.
support ARI, not finished yet
d5b5bce
#4944
As another note, Let's Encrypt is Ending Support for Expiration Notification Emails as of June 4, 2025, which I believe makes this even more relevant.
No branches or pull requests
Hello,
this is a feature request for:
Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension
https://www.ietf.org/archive/id/draft-ietf-acme-ari-02.html
This extension allows CA's to inform the ACME client that a renewal is necessary earlier than normal for example due to an upcoming mass revocation:
For example this would cover various mass revocation events like:
#4936
The alternative is that CA's need to email their users, which then have to
--renew --force
the affected certs.Current status in other projects:
I believe this would be a good addition to the client.
Lukas
The text was updated successfully, but these errors were encountered: