DJANGO-ACL
Django has a built in permissions system, but all the permissions are more directly related to models. This is meant to extend that system by adding permissions, or actions, not related specifically to models.
This also adds an ACL aspect to Django-CMS as an optional
Documentation
Add to INSTALLED APPS
Add the module to your installed apps.
INSTALLED_APS = ( ... 'djangoacl' )
Template Loader
Add the new authentication backend to AUTHENTICATION_BACKENDS in settings.py
TEMPLATE_LOADERS = ( 'skin.template.loaders.filesystem.Loader', 'skin.template.loaders.app_directories.Loader', 'django.template.loaders.filesystem.Loader', 'django.template.loaders.app_directories.Loader', )
Run migrations
$ python manage.py migrate djangoacl
Add the action
Go to http://yoursite/admin/djangoacl/action/add/ and add the action.
Give the action a name. This can be pretty much anything you want but recommend no spaces or special characters. Also probably best not to use anything that matches then normal permission patters such as <action>_<model> or <model>.<action>
Make sure to add any related users or groups.
Request Permission
Request permission in the normal way using the permission_required decorator. See https://docs.djangoproject.com/en/1.8/topics/auth/default/#the-permission-required-decorator
1 maintainer
Metadata
1 maintainer
Release files for django-acl 0.1.3
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 | Actions |
|---|---|---|---|---|
| django-acl-0.1.3.zip | 13.6 kB | Without provenance | Details for django-acl-0.1.3.zip |
Release files / django-acl-0.1.3.zip
| Download URL | django-acl-0.1.3.zip |
|---|---|
| Size | 13.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
66f7f0c39cec97e5c4fcf86567224b87b1fed88848fc697b6ae781054abd917e
|
|
BLAKE2b-256 checksum How to use checksums |
958c692fdef5b19782af118e2f67d381d109363ec3fc44b7fe6d902930b397e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-acl 0.1.3
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.
