django-oidc-provider
django-oauth-toolkit
| django-oidc-provider | django-oauth-toolkit | |
|---|---|---|
| 1 | 6 | |
| 401 | 3,031 | |
| - | 0.8% | |
| 7.4 | 8.2 | |
| 3 months ago | 1 day ago | |
| Python | Python | |
| MIT License | GNU General Public License v3.0 or later |
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-oidc-provider
-
Django app defaults?
The python-oidc-provider package (https://github.com/juanifioren/django-oidc-provider) has another creative way to solve the app-settings/defaults problem. It uses properties to define defaults in a myapp/settings.py file:
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...
-
What to store in database in password files when using login with facebook API.
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
- RuntimeError: Model class django.contrib.contenttypes.models.ContentType doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS. error
-
Authentication with Django REST Framework
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.
-
Authorization in Django, how to approach it as a begginer?
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.
What are some alternatives?
Ory Hydra - OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid.
django-allauth - Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication.
django-registration - An extensible user-registration app for Django.
django-oauth2-provider - Provide OAuth2 access to your app
django-oauth-toolkit - OAuth2 goodies for the Djangonauts! [Moved to: https://github.com/jazzband/django-oauth-toolkit]
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.