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

Add help for the 'Malformed account ID in KeyID header' error

pull/61/head
Richard Körber 2018-03-13 22:57:59 +01:00
parent 7cfcbc99b6
commit a7d6502663
No known key found for this signature in database
GPG Key ID: AAB9FD19C78AA3E0
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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. 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. 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.
* 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.