How to use tls.permission.http in Caddyfile config format?

1. The problem I’m having:

I am using ask directive with on_demand to generate certificate based on user registration. Since it is being deprecated , I would like to use tls.permission.http module mentioning endpoint. Couldn’t find a way to do it in Caddyfile ( non json ) correctly.

Sample config is appreciated.

3. Caddy version:

I am using Caddy 2.8

It’s not been deprecated. Nothing is changing there. It was only the JSON config that was deprecated. The ask option in the Caddyfile will continue to exist.

We did add permission <module> support in the same position as ask but we haven’t had time to add it to the documentation yet. That’s only needed if you use a custom module (i.e. not just a simple HTTP URL).


Yep :point_up:

The ask subdirective in the Caddyfile simply is transformed into the HTTP permission module in JSON, rather than into a literal "ask": "..." key/value. So no changes to the Caddyfile.

1 Like