Fix migration docs

feature/mock
Richard Körber 2019-11-08 10:50:22 +01:00
parent 6dbb407ee2
commit 229801c13d
No known key found for this signature in database
GPG Key ID: AAB9FD19C78AA3E0
1 changed files with 0 additions and 8 deletions

View File

@ -2,8 +2,6 @@
This document will help you migrate your code to the latest _acme4j_ version.
<div class="alert alert-info" role="alert">
## 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).
@ -47,9 +45,3 @@ This document will help you migrate your code to the latest _acme4j_ version.
_acme4j_ 2.0 fully supports the ACMEv2 protocol. Sadly, the ACMEv2 protocol is a major change.
There is no easy recipe to migrate your code to _acme4j_ 2.0. I recommend to have a look at the example, and read this documentation. Altogether, it shouldn't be too much work to update your code, though.
ACMEv1 support will stop on November 1st, 2019!
### "Malformed account ID in KeyID header"
If you try to use your old ACME v1 account location URL in ACME v2, you will get a "Malformed account ID in KeyID header" error. The easiest way to fix this is to register a new account **with your existing account key pair**. You will get your migrated account location URL in return.