github
/
acme4j
mirror of https://github.com/shred/acme4j
1
0
Fork 0
Code Issues Releases Wiki Activity

Remove references to ACMEv1

feature/mock
Richard Körber 2019-11-04 00:22:47 +01:00
parent 3ce5b8bd4f
commit 3c73055084
No known key found for this signature in database
GPG Key ID: AAB9FD19C78AA3E0
3 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
.github/ISSUE_TEMPLATE.md vendored
View File

@ -1,7 +0,0 @@
<!--
Thank you for submitting an issue!
Please state the acme4j version you are using, so we know whether the bug is related to the ACMEv1 or ACMEv2 protocol.
-->

2
README.md
View File

@ -8,8 +8,6 @@ This Java client helps connecting to an ACME server, and performing all necessar
It is an independent open source implementation that is not affiliated with or endorsed by _Let's Encrypt_. It is an independent open source implementation that is not affiliated with or endorsed by _Let's Encrypt_.
**IMPORTANT: Starting November 1st, 2019, all _acme4j_ versions before v2.5 will not work properly any more.** Make sure to update to the latest _acme4j_ version in time. See [here](https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380) and [here](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430) for details. You will find help for migrating your code in the [migration guide](https://shredzone.org/maven/acme4j/migration.html).
## Features ## Features
* Fully [RFC 8555](https://tools.ietf.org/html/rfc8555) compliant * Fully [RFC 8555](https://tools.ietf.org/html/rfc8555) compliant

5
src/site/markdown/migration.md
View File

@ -4,11 +4,6 @@ This document will help you migrate your code to the latest _acme4j_ version.
<div class="alert alert-info" role="alert"> <div class="alert alert-info" role="alert">
**Starting on November 1st, 2019, all _acme4j_ versions before 2.5 will not work properly any more.**
I recommend to update at least to this _acme4j_ version as soon as possible! _Let's Encrypt_ has [announced a sunset date for GET requests](https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauthenticated-resource-gets/74380) on November 1st, 2019. On the same day [access to the ACMEv1 servers](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430) will be restricted.
</div>
## Migration to Version 2.7 ## Migration to Version 2.7
- Note that _acme4j_ has an `Automatic-Module-Name` set in the acme-client and acme-utils modules now. If you have added _acme4j_ to your Java 9+ module dependencies, you'll need to fix your dependency declaration to `org.shredzone.acme4j` (acme-client) and `org.shredzone.acme4j.utils` (acme-utils). - Note that _acme4j_ has an `Automatic-Module-Name` set in the acme-client and acme-utils modules now. If you have added _acme4j_ to your Java 9+ module dependencies, you'll need to fix your dependency declaration to `org.shredzone.acme4j` (acme-client) and `org.shredzone.acme4j.utils` (acme-utils).