Another question about the http-01 payload / contents about acmephp HOT 2 CLOSED

Hi @kevinquinnyo !

That's a very interesting question indeed :) ! Thanks for your interest in the library and for your feedbacks, that's really appreciated!

What is important to note here is that the ACME protocol is still not yet fully stable. While the document you linked is still mostly valid, the protocol has changed since then (and I think it's a link from the documentation, I should change that :) ). You can see on top of it that the document you linked expired on 22/01/2016.

I suggest you read the last version of the protocol, defined at https://tools.ietf.org/html/draft-ietf-acme-acme-02 (and expiring in september), especially this part: https://tools.ietf.org/html/draft-ietf-acme-acme-02#section-7.2.

As you can see at line https://github.com/acmephp/acmephp/blob/master/src/Core/AcmeClient.php#L125, we are not using the simpleHttp challenge but the http-01 one, defined in the new protocol version as:

The path at which the resource is provisioned is comprised of the
fixed prefix ".well-known/acme-challenge/", followed by the "token"
value in the challenge.  The value of the resource MUST be the ASCII
representation of the key authorization.

And we are doing that by encoding the account key here: https://github.com/acmephp/acmephp/blob/master/src/Core/AcmeClient.php#L115

The payload we provide using the AcmeClient class is this ASCII representation of the key authorization.

I hope this answer your question :) . Don't hesitate to ask if you have another issue, I would be glad to give a hand when you need it.

PS : you can close the issue if it answers your question :) .

from acmephp.

@tgalopin Thanks! That was incredibly helpful and clears it up 100% for me.

from acmephp.