django-oauth-toolkit VS django-rest-framework

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.

The GitHub Discussion: link

Django’s "batteries-included" philosophy makes it an excellent choice for API development. With Django REST Framework (DRF), you get:

I am maintaining a Python codebase that is based on Django and Django REST Framework (DRF). The codebase uses Nix for development, testing, CI/CD and packaging.

Django Rest framework

Explore the Django REST Framework Documentation for advanced topics.

I've seen some companies using React with Django REST Framework [1], to keep the benefits of Django (I'm not a Django dev so I will have to guess, the ORM and project structure?) while having a strong separation between front and back (separate projects, teams, deploys, etc).

[1] https://www.django-rest-framework.org

Django REST Framework is a powerful and flexible toolkit for building Web APIs using Django, the popular high-level Python web framework. Zuplo proudly sponsors the DRF project to continue improving the Django API development ecosystem.

I think people tend to consider Django either for building old-school, industrial-strength monolith apps or for APIs and using something like React for the front-end. I’m here to tell you that plain old Django is a great option even for your personal websites! In my opinion, if you need a database, you should use Django1.

This post will extend Django REST Framework's ViewSet and SimpleRouter to provide a Rails-like request handler class + resource routing in server-render Django applications. It also features form-level method spoofing for PUT, PATCH and DELETE requests via custom middleware.

Django Rest Framework