django-oauth-toolkit VS django-reversion

View on GitHub

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...

You would need to store whatever identifier the oauth provider gives you along with access and refresh tokens. That said, I wouldn't try to implement this from scratch, since it is not trivial. Try django-oauth-toolkit

Thankfully you don't need to implement this giant standard yourself. You can use the excellent Django OAuth Toolkit package. They also have a specific section in their documentation for using it with DRF.

I would suggest token auth as it is stateless, secure and can be used on multiple devices. OAuth/OAuth2 is the industry standard at the moment but you can also use a simple JWT token signature. On top of this, Django REST framework offers a lot of libraries for this purpose e.g. django-rest-framework-simplejwt, django-rest-framework-social-oauth2, django-oauth-toolkit, and more.

django-reversion ([OPTION] For object history and reversion feature, please select right version by your django, see changelog )

I did the initial installation steps and created the initial revisions, but then when I save a model in django shell, the new revision is not created:

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.

Reversion - looks simple enough to use but not sure how easy it would be to modify it if needed.

Have you checked out django-reversion?

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?