Caddy-authz is an authorization middleware for Caddy, it's based on https://github.com/casbin/casbin.
go get github.com/casbin/caddy-authz
localhost {
route {
authz "/folder/to/caddy_binary/authz_model.conf" "/folder/to/caddy_binary/authz_policy.csv"
}
respond "Hello, world!"
...
}
or
{
order authz before respond
}
localhost {
authz "/folder/to/caddy_binary/authz_model.conf" "/folder/to/caddy_binary/authz_policy.csv"
respond "Hello, world!"
...
}
The authz
directive specifies the path to Casbin model file (.conf) and Casbin policy file (.csv). The Casbin model file describes access control models like ACL, RBAC, ABAC, etc. The Casbin policy file describes the authorization policy rules. For how to write these files, please refer to: https://github.com/casbin/casbin#get-started
-
cd
into the folder ofcaddy
binary. -
Put your Casbin model file authz_model.conf and Casbin policy file authz_policy.csv into this folder.
-
Add
authz
directive to your Caddyfile like:
localhost:666 {
route {
authz "authz_model.conf" "authz_policy.csv"
}
respond "Hello, world!"
...
}
- Run
caddy
and enjoy.
Note: This plugin only supports HTTP basic authentication to get the logged-in user name, if you use other kinds of authentication like OAuth, LDAP, etc, you may need to customize this plugin.
The authorization determines a request based on {subject, object, action}
, which means what subject
can perform what action
on what object
. In this plugin, the meanings are:
subject
: the logged-on user nameobject
: the URL path for the web resource like "dataset1/item1"action
: HTTP method like GET, POST, PUT, DELETE, or the high-level actions you defined like "read-file", "write-blog"
For how to write authorization policy and other details, please refer to the Casbin's documentation.
This project is under Apache 2.0 License. See the LICENSE file for the full license text.