django-oauth-toolkit VS python-jose

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.

Everything that's in `/app` is the compiled application; changes should be made locally and redeployed. Looking at the `python-jose` package, they've made the changes already (https://github.com/mpdavis/python-jose/blob/master/jose/jwt.py) so should be able to update `python-jose` locally (`requirements.txt`, I think?) and re-deploy to solve this.

I use JOSE for the JWT token creation https://github.com/mpdavis/python-jose

If you're using a API Gateway REST API, then yeah, a lambda authorizer is the way to go. You can use something like python-jose to work with the JWTs.