The following is outdated! See the comment below for notes updated on 2nd December 2015 . Some notes on using the webroot domain verification process with the test ACME server (don’t do this on a live server yet!) in case anyone else wants to have a play with this — this method will be best suited f…

@eva2000 , on Monday changes were merged into the master branch of the client to kill off the old challenges using jose+json and now require text/plain (or no Content-Type at all). These changes were pushed to PyPI in the last 24 hours and now effect letsencrypt-auto.

application/jose+json was for the SimpleHTTP challenge. A recent spec revision replaced SimpleHTTP with http-01, which fixes a signature reuse issue. In theory, the required Content-Type is application/jose+json for SimpleHTTP challenges (which will soon go away), and text/plain for http-01, which i…

thanks @bmw and @jsha that’s a huge change especially for folks doing their integrations. You also need a way to convey such major changes to everyone too :smile: if i updated the client properly via wiping virtualenv and reinstall, then looks like letsencrypt still currently accepts jose+json type…

That’s a good point about trying to directly convey these changes to the Let’s Encrypt community. I think no matter what we do, some people fail to hear about the change, but we can certainly do better. Do you have any suggestions on how we should go about doing this? What if we tried to made a post…

or just dont care about it, I mean what counts is the content.

it said for me that it required that as well, but @bmw states that the server should reject json and that, but I think why care at all? just evaluate the size and the content that is stuff that cannot be wrong because if it was the data is wrong, while the conent header can be anything, technicaly.

Correction: It appears that boulder, the Let’s Encrypt server, is accepting both application/jose+json and text/plain. If and only if you’re running letsencrypt using the manual authenticator, the client attempts to verify the challenge has been set up correctly before contacting boulder. This self …

but WHY does bolder and/or the client even CARE?

[image] bmw: That's a good point about trying to directly convey these changes to the Let's Encrypt community. I think no matter what we do, some people fail to hear about the change, but we can certainly do better. Do you have any suggestions on how we should go about doing this? What if we tri…

Using the webroot domain verification method

Server

PeterMount November 5, 2015, 5:31pm 34

When I used the client on 2 new beta domains yesterday the client required text/plain then

Topic		Replies	Views
Letsencrypt Webroot Authentication Tested on Beta invited/whitelisted domain Issuance Tech	6	16337	December 2, 2015
[Webroot] Error: The client lacks sufficient authorization Help	11	5543	January 6, 2016
New to LetsEncrypt Help	33	3145	September 29, 2021
Webroot plugin : The client lacks sufficient authorization Uncategorized	37	37335	April 25, 2017
I just want a certificate Uncategorized	26	11350	December 11, 2015

Using the webroot domain verification method

Related topics