bouncer
Simple Declarative Authentication DSL inspired by Ryan Bates’ excellent cancan library
Introduction
Meet bouncer.
bouncer is your faithful servant. Big, burly, trustworthy – smarter than he looks, but very effective in what he does. You just have to talk simply to him. For example:
from bouncer import authorization_method
from bouncer.constants import *
@authorization_method
def authorize(user, they):
if user.is_admin:
they.can(MANAGE, ALL)
else:
they.can(READ, ALL)
they.cannot(READ, 'TopSecretDocs')
def if_author(article):
return article.author == user
they.can(EDIT, 'Article', if_author)
And once you have that setup, you can ask questions like:
jonathan = User(name='jonathan',admin=False)
marc = User(name='marc',admin=False)
article = Article(author=jonathan)
print can(jonathan, EDIT, article) # True
print can(marc, EDIT, article) # False
# Can Marc view articles in general?
print can(marc, VIEW, Article) # True
Installation
pip install bouncer
Defining Abilities
Alternative syntax
dict syntax
You can also use an alternative dict syntax. The following is equivalent to above:
@authorization_method
def authorize(user, they):
if user.is_admin:
they.can(MANAGE, ALL)
else:
they.can(READ, ALL)
they.can(EDIT, Article, author=user)
You can add multiple conditions to the dict:
they.can(READ, Article, published=True, active=True)
Strings instead of classes
You can use strings instead of classes. This means you do not need to import a bunch of files you are not using in initialization
@authorization_method
def authorize(user, they):
if user.is_admin:
they.can(MANAGE, ALL)
else:
they.can(READ, ALL)
# Notice that I am using a string here
they.can(EDIT, 'Article', author=user)
Combining Rules
You can (are encouraged to) combine similar rules on a single line:
they.can((EDIT,READ,DELETE),(Article,Photo))
Combining Abilities
It is possible to define multiple abilites for the same resource. This is particularly useful in combination with the cannot method
they.can(MANAGE, ALL)
then.cannot(DELETE, ('USER', 'ACCOUNT'))
Checking Abilities
There are two main ways for checking for authorization. can (and its brother cannot) and ensure
can returns a boolean
ensure will raise an AccessDenied Exception
from bouncer import can, ensure
from bouncer.constants import *
jonathan = User(name='jonathan',admin=False)
# can jonathan edit articles in general
can(jonathan, EDIT, Article)
# ensure jonathan edit articles in general -- otherwise we are going to throw an exception
ensure(jonathan, EDIT, Article)
article = Article(author=jonathan)
# can jonathan delete this specific article
can(jonathan, EDIT, article)
Decorating your User Model
Optionally, you can add helper methods into your User model by using @authorization_target
For example:
from bouncer import authorization_target
@authorization_target
class User(object):
def __init__(self, **kwargs):
self.id = kwargs.get('id', 1)
self.name = kwargs.get('name', '')
self.admin = kwargs.get('admin', False)
pass
@property
def is_admin(self):
return self.admin
jonathan = User(name='jonathan',admin=False)
marc = User(name='marc',admin=False)
article = Article(author=jonathan)
print jonathan.can(EDIT,article) # True
print marc.can(EDIT,article) # False
Flask
If you use Flask, I am currently working on a Flask extension – follow its progress here: flask-bouncer.
Questions / Issues
Feel free to ping me on twitter: @tushman or add issues or PRs at https://github.com/jtushman/bouncer
Metadata
Release files for bouncer 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| bouncer-0.1.12.tar.gz | 5.5 kB | Without provenance | Details |
Release files / bouncer-0.1.12.tar.gz
| Download URL | bouncer-0.1.12.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a7753bf9e6e39063595529334dffef5b00c8e7760b9ac357172717878614a10
|
|
BLAKE2b-256 checksum How to use checksums |
8b9f7c4ee715ff73503937a9979a16a19574aaefc9acbdd2f7f728190c7974e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bouncer 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.