Database-agnostic extension for Flask to support role-based authentication of users.
Links
Revisions
0.85
Updated to Flask 0.8 new naming scheme of using flask.ext for sqlalchemy.
Fixed issue with importing sqlalchemy models.
0.8
Major revision.
Not storing the entire user in the session anymore (which was convenient but bad practice) but only its __dict__.
As a result of the above, the get_current_user call is now gone and replaced by get_current_user_data call. Similar functionality to the original call can now be obtained by doing AuthUser.load_current_user().
Created SQLAlchemy plug-and-play model using constructor.
Small bugfixes.
0.7
Added tests, permission example, bunch of bugfixes.
0.6
Added permission model, added examples, first release on PyPI.
0.1 - 0.5
Logging in, session management, encryption, etc.
1 maintainer
Metadata
1 maintainer
Release files for Flask-Auth 0.85
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 |
|---|---|---|---|---|
| Flask-Auth-0.85.tar.gz | 47.0 kB | Without provenance | Details for Flask-Auth-0.85.tar.gz |
Release files / Flask-Auth-0.85.tar.gz
| Download URL | Flask-Auth-0.85.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a749c1f021a731ba8b40656bf863093840fa8cb4f1d2675571c1073357245285
|
|
BLAKE2b-256 checksum How to use checksums |
b5f50be3fa48160222a538d7db1715ea88ca8674aa2dbfcb2ba10b9cf47d16cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Flask-Auth 0.85
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.
