Podcast
Root Causes 318: What Is ACME Renewal Information (ARI)?
Hosted by
Jason Soroko
Fellow
Original broadcast date
July 18, 2023
ACME is a functional and widely supported protocol for certificate provisioning and installation. A new extension to the protocol will help automate renewals. In this episode we explain ACME Renewal Information (ARI).
Podcast transcript
Lightly edited for flow and brevity.
TCTim CallanWe want to talk today about ACME. We talk about ACME a lot, don't we?
TCTim CallanAnd there's widespread support. There's a lot of reliability. You can use ACME and it’ll work. So, ACME is wonderful. everything's hunky dory. It's absolutely perfect so there's nothing to say about ACME, Jay?
TCTim CallanUnfortunately not.
Now, there's obviously a lot of other ways to do that. There's all kinds of IT tools to do things that are far better than a cron job. A lot more reliably things that can be monitored, hey, if there's a problem, if things had to back up, checking logs if there was an error. There’s all kinds of proper IT ways to do things. That's not really the topic here, Tim. I think what we're going to be talking about is what's going on in the ACME world to help out with renewals?
TCTim CallanSo there's a concept that's called ACME Renewal Information and oftentimes, people just refer to it as ARI. And ARI is supposed to build the concept of renewal into the ACME protocol. Because right now, that's not there. Right now, in ACME’s perspective, if I'm getting a new certificate for the exact same use case, the exact same domain, the exact same environment and server every 60 days into perpetuity, in ACME’s world, each of these is just its own independent event and ARI starts to introduce a little bit of a lifecycle concept into the ACME protocol.
TCTim CallanAnd what are the advantages of this?
Basically, you as the consumer of a publicly trusted certificate, and you're using your ACME client of choice, Certbot being an example. If ARI were implemented, what you’d presumably be able to do is use the client to actually ask the server, hey, what is my renewal info and in fact, I believe the method being proposed here is called renewal info and that basically would be a command sent off on your behalf to the server by the client. And then the server would then come back to you and say, oh, here is your, I think it's gonna potentially to come back with two things that need to be parsed. And ultimately renewal info is going to be sent by via GET command, and then the URL response can be parsed. And that parsing of that information will give you hey, this is the renewal info. This is the renewal window in which you are either in or not in and so the client would need to parse that URL to determine what the window is, and then how to act upon it.
And here's the oversimplified part. Part of the parsing procedure would then be, hey, am I within the renewal window, meaning, I have specified that I want to renew after 60 days, after 65 days, after 70 days. Yes, the servers will respond. You're renewal info will say to you, you are within the renewal window past the 60 days, or 65 days, or whatever it happens to be, and then the client can make a decision and go, oh, thank you for that information. I am now going to issue a renewal command through the ACME client and then use the standard ACME protocol to do a renewal function, which, of course, is not renewal because ACME doesn't really have a concept of renewal. This is the chicken and egg problem that it's trying to break is that it's renewal information, we're not really adding renewal concept into ACME as much as we are being able to configure a renewal window and be able to pull, hey, Mr. Server you know when my last cert was issued. Can you tell me when my renewal window is based off of that, and then the client not having to know anything can then act upon that information, Tim? That's what it's all about.
TCTim CallanAnd so, I'm not sure so much that this is going to be a function of preventing outages due to renewal as it is just making life easier for the people who have to put together and administer and run these systems. Do you think that's right?
TCTim CallanSo in that sense, maybe I'm wrong. Maybe you're saying that there is a reliability gain that comes out of this. That there is less likely to be an error or a flaw or an unfortunate missed renewal that occurs.
TCTim CallanAnd that’s true in any automation situation. If you screw up the configuration, you're in trouble. That's sort of the nature of the beast of automation.
TCTim CallanAnd it's also very early days, and I get the impression - again, I don't have hard numbers to put behind this, but I get the impression that adoption of ARI at this point is extremely scarce. And I think we're looking at something that we're going to see a trend. I think this is going to become much more common. I also think we've got spotty support in terms of the systems and the software you would need that knows how to use it and I think we should look to see this one tracking up over time and as that happens, this ARI becoming a reliable part of your IT toolkit, just like your more basic set of ACME commands are today.
TCTim CallanAll right. Well, there you go. That's ACME Renewal Information, aka ARI. Thank you very much, Jay.