This is a copy of issue 1863 , moved here for discussion. Authentication in Caddy currently seems to be a bit of a mess. I would like to introduce you to a concept of how Caddy could improve this situation drastically: The Caddy core is responsible for checking permissions on requests, plugins prov…

I was planning to implement something similar to this just combined with the webdav plugin as a standalone server, but have decided that I will implement this as a Caddy plugin. (That is why I chose the “Plugin” category instead of “Coding”) There is of course a huge drawback in implementing this a…

Thanks Daniel, for writing this up! I wanted to shed some light on one thing: [image] dhaavi: There is of course a huge drawback in implementing this as a plugin, instead of putting the core procedures into the Caddy core itself: All backends must be implemented directly in this plugin and can…

It’s been a while, I’ve been very busy lately. So here’s an update: I finished the first version of the plugin and am already using it in production. I use it for handing over authentication for the filemanager and webdav plugin to my backend. Have a look: GitHub - dhaavi/caddy-permission: Authe…

Cool! When will you have some docs up about how to use it? As for the client certificates protecting only some paths, how do you intend to do that?

Soon, I hope :wink: I do not know yet. Depends on how browsers react to optional client certificates.

Caddy Community

Improve Caddy auth system

Plugins

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled