Hi there, I’m trying to get an in-depth understanding of how ACME and LetsEncrypt works and therefore writing my own ACME client that I’m trying to get running with LetsEncrypt. The ACME RFC is rather horrible, in my opinion. All examples just show half of the actual work and no actual message is …

Okok, I got it, I think. First new-reg gives “link” terms-of-service header field, which points to the TOS URI. Then I can submit a second post to the URL that is given as Location in the 409 new-reg response in which I re-post the subscription information (with the correct URL). It’s in the docs, …

Note that the ACME spec moved to https://ietf-wg-acme.github.io/acme/ . This doesn’t address the inconsistency you mentioned, but other things might have changed. To add to what @serverco said, I would specifically look at the “Libraries” section in that thread, which contains low-level libraries fo…

Hi Johannes, I ran into the same problem. Your post saved my night. When trying to submit a new-authz, I got this response: RESPONSE STATUS: 403 HEADERS: [('Server', 'nginx'), ('Content-Type', 'application/problem+json'), ('Content-Length', '137'), ('Boulder-Request-Id', 'nUDq2tctipap93zUx8nFvw…

[image] guti: b) Detailed and up-to-date documentation on the difference between the implementation of Boulder and the ACME protocol; letsencrypt/boulder/blob/main/docs/acme-divergences.md # Boulder divergences from ACME While Boulder attempts to implement the ACME specificat…

Hi Andy, Thank you for the message. Yes I went through this page last night. It's just... incomplete... It says in the version 04 of the protocol ( draft-ietf-acme-acme-04 ) that: 5.2. Request Authentication All ACME requests with a non-empty body MUST encapsulate the body in a JWS object, s…

I must admit I’d missed all the “kid” stuff that came in v4. I wrote the bulk of my client before v4 came out. perhaps @cpu can comment on that. For general help in developing a client you may be better posting in the “client dev” forum. What language are you developing a client in ?

Hi @serverco , @guti , I think you’ve identified a place where the divergences document isn’t capturing a Boulder behaviour that doesn’t match the latest draft. I’ll look at fixing that . In the future filing an issue on the Boulder repo about the divergence is the best path for this sort of issue. T…

@serverco I wrote in python. If you ask why I write another python implementation when there’s already an official one, then the answer will be: Certbot aims at providing a command line console which still requires human interventions to acquire a certificate, I.e. pressing ENTER after copying and …

Hi @cpu , Thank you for the reply. I’ll post stuff at the designated area if I discover another mismatch. You guys are doing a great job. I’d been comparing the pricing of the CAs for a while until I accidentally discovered the existence of LetsEncrypt when browsing the docs of BeautifulSoup4. I …

Agreeing to subscriber agreement

Issuance Tech

serverco February 28, 2016, 2:44pm 3

What language are you developing your client in ? it may be worth looking at a similar working example in the alternate clients

Topic		Replies	Views
Missing API Documentation Help	4	1208	December 9, 2017
New-authz 403 response Client dev	6	1661	December 13, 2017
Registration Rate Limit in Staging Using Python ACME Client Help	20	2880	June 20, 2018
ACME Protocol (RFC 8555) and EAB Client dev	19	4998	November 15, 2022
Problems with my new perl ACME2 client Client dev	8	1556	March 21, 2020

Agreeing to subscriber agreement

Related topics