Update the location of Revel plugin.
1 file changed
tree: 89e5dc1eaab57472d13c88ebcb8a0ce65ff89ea7
  1. config/
  2. examples/
  3. file-adapter/
  4. model/
  5. persist/
  6. rbac/
  7. util/
  8. .gitignore
  9. .travis.yml
  10. casbin-logo.png
  11. enforcer.go
  12. enforcer_safe.go
  13. enforcer_synced.go
  14. enforcer_test.go
  15. error_test.go
  16. internal_api.go
  17. LICENSE
  18. management_api.go
  19. management_api_test.go
  20. model_b_test.go
  21. model_test.go
  22. rbac_api.go
  23. rbac_api_test.go
  24. rbac_api_with_domains.go
  25. rbac_api_with_domains_test.go
  26. README.md
  27. ui_model_editor.png
  28. ui_policy_editor.png
README.md

Casbin

Go Report Card Build Status Coverage Status Godoc Release Gitter Patreon Sourcegraph Badge

News: Casbin is also started to port to Java, contribution is welcomed. See: https://github.com/casbin/jcasbin

casbin Logo

Casbin is a powerful and efficient open-source access control library for Golang projects. It provides support for enforcing authorization based on various access control models.

Supported by Auth0

If you want to easily add authentication and authorization to your Go projects, feel free to check out Auth0's Go SDK and free plan at auth0.com/overview

Table of contents

Supported models

  1. ACL (Access Control List)
  2. ACL with superuser
  3. ACL without users: especially useful for systems that don't have authentication or user log-ins.
  4. ACL without resources: some scenarios may target for a type of resources instead of an individual resource by using permissions like write-article, read-log. It doesn't control the access to a specific article or log.
  5. RBAC (Role-Based Access Control)
  6. RBAC with resource roles: both users and resources can have roles (or groups) at the same time.
  7. RBAC with domains/tenants: users can have different role sets for different domains/tenants.
  8. ABAC (Attribute-Based Access Control): syntax sugar like resource.Owner can be used to get the attribute for a resource.
  9. RESTful: supports paths like /res/*, /res/:id and HTTP methods like GET, POST, PUT, DELETE.
  10. Deny-override: both allow and deny authorizations are supported, deny overrides the allow.
  11. Priority: the policy rules can be prioritized like firewall rules.

How it works?

In Casbin, an access control model is abstracted into a CONF file based on the PERM metamodel (Policy, Effect, Request, Matchers). So switching or upgrading the authorization mechanism for a project is just as simple as modifying a configuration. You can customize your own access control model by combining the available models. For example, you can get RBAC roles and ABAC attributes together inside one model and share one set of policy rules.

The most basic and simplest model in Casbin is ACL. ACL's model CONF is:

# Request definition
[request_definition]
r = sub, obj, act

# Policy definition
[policy_definition]
p = sub, obj, act

# Policy effect
[policy_effect]
e = some(where (p.eft == allow))

# Matchers
[matchers]
m = r.sub == p.sub && r.obj == p.obj && r.act == p.act

An example policy for ACL model is like:

p, alice, data1, read
p, bob, data2, write

It means:

  • alice can read data1
  • bob can write data2

Features

What Casbin does:

  1. enforce the policy in the classic {subject, object, action} form or a customized form as you defined, both allow and deny authorizations are supported.
  2. handle the storage of the access control model and its policy.
  3. manage the role-user mappings and role-role mappings (aka role hierarchy in RBAC).
  4. support built-in superuser like root or administrator. A superuser can do anything without explict permissions.
  5. multiple built-in operators to support the rule matching. For example, keyMatch can map a resource key /foo/bar to the pattern /foo*.

What Casbin does NOT do:

  1. authentication (aka verify username and password when a user logs in)
  2. manage the list of users or roles. I believe it's more convenient for the project itself to manage these entities. Users usually have their passwords, and Casbin is not designed as a password container. However, Casbin stores the user-role mapping for the RBAC scenario.

Installation

go get github.com/casbin/casbin

Documentation

See: Our Wiki

Get started

  1. New a Casbin enforcer with a model file and a policy file:

    e := casbin.NewEnforcer("path/to/model.conf", "path/to/policy.csv")
    

Note: you can also initialize an enforcer with policy in DB instead of file, see Persistence section for details.

  1. Add an enforcement hook into your code right before the access happens:

    sub := "alice" // the user that wants to access a resource.
    obj := "data1" // the resource that is going to be accessed.
    act := "read" // the operation that the user performs on the resource.
    
    if e.Enforce(sub, obj, act) == true {
        // permit alice to read data1
    } else {
        // deny the request, show an error
    }
    
  2. Besides the static policy file, Casbin also provides API for permission management at run-time. For example, You can get all the roles assigned to a user as below:

    roles := e.GetRoles("alice")
    

See Policy management APIs for more usage.

  1. Please refer to the _test.go files for more usage.

Policy management

Casbin provides two sets of APIs to manage permissions:

  • Management API: the primitive API that provides full support for Casbin policy management. See here for examples.
  • RBAC API: a more friendly API for RBAC. This API is a subset of Management API. The RBAC users could use this API to simplify the code. See here for examples.

We also provide a web-based UI for model management and policy management:

model editor

policy editor

Policy persistence

In Casbin, the policy storage is implemented as an adapter (aka middleware for Casbin). To keep light-weight, we don't put adapter code in the main library. A complete list of Casbin adapters is provided as below. Any 3rd-party contribution on a new adapter is welcomed, please inform us and I will put it in this list:)

AdapterTypeAuthorDescription
File Adapter (built-in)FileCasbinPersistence for .CSV (Comma-Separated Values) files
Xorm AdapterORMCasbinMySQL, PostgreSQL, TiDB, SQLite, SQL Server, Oracle are supported by Xorm
Gorm AdapterORMCasbinMySQL, PostgreSQL, Sqlite3, SQL Server are supported by Gorm
Beego ORM AdapterORMCasbinMySQL, PostgreSQL, Sqlite3 are supported by Beego ORM
MongoDB AdapterNoSQLCasbinPersistence for MongoDB
Cassandra AdapterNoSQLCasbinPersistence for Apache Cassandra DB
Consul AdapterKV store@ankitm123Persistence for HashiCorp Consul
Redis AdapterKV storeCasbinPersistence for Redis
Protobuf AdapterStreamCasbinPersistence for Google Protocol Buffers
RQLite AdapterSQLEDOMO SystemsPersistence for RQLite
PostgreSQL AdapterSQLGoingPersistence for PostgreSQL
RethinkDB AdapterNoSQL@adityapandey9Persistence for RethinkDB

For details of adapters, please refer to the documentation: https://github.com/casbin/casbin/wiki/Policy-persistence

Policy consistence between multiple nodes

We support to use etcd to keep consistence between multiple Casbin enforcer instances. Please see: https://github.com/casbin/etcd-watcher

Role manager

We support different implementations of a RBAC role manager. The currently supported adapters are:

Role managerDescription
Default role managerSupports role hierarchy
Session role managerSupports role hierarchy, time-range-based sessions

For developers: all role managers must implement the RoleManager interface.

To use a custom role manager implementation:

type myCustomRoleManager struct {} // assumes the type satisfies the RoleManager interface

func newRoleManager() rbac.RoleManagerConstructor {
	return func() rbac.RoleManager {
		return &myCustomRoleManager{}
	}
}

e := casbin.NewEnforcer("path/to/model.conf", "path/to/policy.csv")
e.SetRoleManager(newRoleManager())

Multi-threading

If you use Casbin in a multi-threading manner, you can use the synchronized wrapper of the Casbin enforcer: https://github.com/casbin/casbin/blob/master/enforcer_synced.go.

It also supports the AutoLoad feature, which means the Casbin enforcer will automatically load the latest policy rules from DB if it has changed. Call StartAutoLoadPolicy() to start automatically loading policy periodically and call StopAutoLoadPolicy() to stop it.

Benchmarks

The overhead of policy enforcement is benchmarked in model_b_test.go. The testbed is:

Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2601 Mhz, 4 Core(s), 8 Logical Processor(s)

The benchmarking result of go test -bench=. -benchmem is as follows (op = an Enforce() call, ms = millisecond, KB = kilo bytes):

Test caseSizeTime overheadMemory overhead
ACL2 rules (2 users)0.015493 ms/op5.649 KB
RBAC5 rules (2 users, 1 role)0.021738 ms/op7.522 KB
RBAC (small)1100 rules (1000 users, 100 roles)0.164309 ms/op80.620 KB
RBAC (medium)11000 rules (10000 users, 1000 roles)2.258262 ms/op765.152 KB
RBAC (large)110000 rules (100000 users, 10000 roles)23.916776 ms/op7.606 MB
RBAC with resource roles6 rules (2 users, 2 roles)0.021146 ms/op7.906 KB
RBAC with domains/tenants6 rules (2 users, 1 role, 2 domains)0.032696 ms/op10.755 KB
ABAC0 rule (0 user)0.007510 ms/op2.328 KB
RESTful5 rules (3 users)0.045398 ms/op91.774 KB
Deny-override6 rules (2 users, 1 role)0.023281 ms/op8.370 KB
Priority9 rules (2 users, 2 roles)0.016389 ms/op5.313 KB

Examples

ModelModel filePolicy file
ACLbasic_model.confbasic_policy.csv
ACL with superuserbasic_model_with_root.confbasic_policy.csv
ACL without usersbasic_model_without_users.confbasic_policy_without_users.csv
ACL without resourcesbasic_model_without_resources.confbasic_policy_without_resources.csv
RBACrbac_model.confrbac_policy.csv
RBAC with resource rolesrbac_model_with_resource_roles.confrbac_policy_with_resource_roles.csv
RBAC with domains/tenantsrbac_model_with_domains.confrbac_policy_with_domains.csv
ABACabac_model.confN/A
RESTfulkeymatch_model.confkeymatch_policy.csv
Deny-overriderbac_model_with_deny.confrbac_policy_with_deny.csv
Prioritypriority_model.confpriority_policy.csv

How to use Casbin as a service?

  • Go-Simple-API-Gateway: A simple API gateway written by golang, supports for authentication and authorization
  • Casbin Server: Casbin as a Service via RESTful, only exposed permission checking API

Our adopters

Web frameworks

  • Beego: An open-source, high-performance web framework for Go, via built-in plugin: plugins/authz
  • Caddy: Fast, cross-platform HTTP/2 web server with automatic HTTPS, via plugin: caddy-authz
  • Gin: A HTTP web framework featuring a Martini-like API with much better performance, via plugin: authz
  • Revel: A high productivity, full-stack web framework for the Go language, via plugin: auth/casbin
  • Echo: High performance, minimalist Go web framework, via plugin: echo-authz (thanks to @xqbumu)
  • Iris: The fastest web framework for Go in (THIS) Earth. HTTP/2 Ready-To-GO, via plugin: casbin (thanks to @hiveminded)
  • Negroni: Idiomatic HTTP Middleware for Golang, via plugin: negroni-authz
  • Tango: Micro & pluggable web framework for Go, via plugin: authz
  • Chi: A lightweight, idiomatic and composable router for building HTTP services, via plugin: chi-authz
  • Macaron: A high productive and modular web framework in Go, via plugin: authz
  • DotWeb: Simple and easy go web micro framework, via plugin: authz
  • Baa: An express Go web framework with routing, middleware, dependency injection and http context, via plugin: authz

Others

License

This project is licensed under the Apache 2.0 license.

Contact

If you have any issues or feature requests, please contact us. PR is welcomed.

Donation

Patreon

Alipay Wechat