From a7d65026630d22003142f1820a3a2a69cae73200 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Richard=20K=C3=B6rber?= Date: Tue, 13 Mar 2018 22:57:59 +0100 Subject: [PATCH] Add help for the 'Malformed account ID in KeyID header' error --- src/site/markdown/migration.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/src/site/markdown/migration.md b/src/site/markdown/migration.md index a7c0a3b6..f1b15e01 100644 --- a/src/site/markdown/migration.md +++ b/src/site/markdown/migration.md @@ -8,9 +8,6 @@ _acme4j_ 2.0 fully supports the ACMEv2 protocol. Sadly, the ACMEv2 protocol is a 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. -## Migration from Version 2.0-SNAPSHOT (GitHub master branch) +### "Malformed account ID in KeyID header" -* The `Session` object has been split into `Session` and `Login`. The `Session` now only tracks the communication, and does not need an account key pair any more. -* To get a `Login` to an existing `Account`, use `Session.login()` with the account key pair and account URL. -* If you create a new `Account` using the `AccountBuilder`, you must pass in the key pair via `AccountBuilder.useKeyPair()`. -* You can find all resource bind methods in `Login` now. +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.