django-oauth-toolkit
django-reversion
Our great sponsors
django-oauth-toolkit | django-reversion | |
---|---|---|
6 | 7 | |
3,007 | 2,964 | |
1.0% | - | |
8.4 | 7.1 | |
9 days ago | 28 days ago | |
Python | Python | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-oauth-toolkit
-
The Best GitHub Repositories For Django Developers.
View on GitHub
-
SSO should be table stakes
Just to be clear: I'm asking for LDAP to be one possible choice. If an installation wants to use LDAP BIND they can use that, or if the want to use SAML they could use that, or OATH. But not at the same time: you get to choose one.
Django Authentication system for example has a User object that allows different backends to feed into it:
* https://django-auth-ldap.readthedocs.io/
* https://django-oauth-toolkit.readthedocs.io/
* https://stackoverflow.com/questions/22668434/saml-with-djang...
django-reversion
-
The Best GitHub Repositories For Django Developers.
django-reversion ([OPTION] For object history and reversion feature, please select right version by your django, see changelog )
-
Tracking changes to all models in Django
I tried django-reversion, django-simple-history, django-audit-log, django-historicalrecords, but I fail to understand how and why I should use each of these packages as some of them seem like an overkill for the requirements. So, after two days of searching and reading through numerous posts about how I should be tracking model changes, I have basically done nothing.
-
Django package for creating data history or checkpoints for database model
Searching djangopackages.org I was confoosed by django-field-history, "A Django app to track changes to a model field.", and similar apps django-reversion and django-simple-history, I think these are tracking changes to the model itself--the code--inside of admin? Like if you created a Poll which saved results to the database, and later wanted to change one of the Poll questions?
- create a timeline for model object changes
What are some alternatives?
django-allauth - Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication.
django-simple-history - Store model history and view/revert changes from admin site.
django-oauth2-provider - Provide OAuth2 access to your app
authlib - The ultimate Python library in building OAuth, OpenID Connect clients and servers. JWS,JWE,JWK,JWA,JWT included.
python-social-auth - Social auth made simple
django-auth-adfs - A Django authentication backend for Microsoft ADFS and AzureAD
django-graphql-auth - Django registration and authentication with GraphQL.
Flask-OAuthlib - YOU SHOULD USE https://github.com/lepture/authlib
OAuthLib - A generic, spec-compliant, thorough implementation of the OAuth request-signing logic
python-oauth2 - A fully tested, abstract interface to creating OAuth clients and servers.
django-audit-log - Audit log for your Django models
sanction - A dead simple OAuth2 client implementation.