Hello, FYI django-two-factor-auth builds upon django-otp; they aren't alternatives.
This is an ambitious project. I suggest to start by getting a better understanding of what these libraries do, what the different scenarios for two factor authentication are, and writing a DEP to describe the APIs that would be added to Django. Look at the current public APIs of django.contrib.auth and figure out what would be needed to support 2FA with similar principles. Starting from the lower layers — the equivalent of django-otp — seems (to me) to be a better way to go about this, but perhaps this is just a bottom-up vs top-down thing. Anyway, I suspect that a DEP that boils down to “merge django-two-factor-auth into Django” and includes integration with arbitrarily chosen commercial services would face some resistance; you need more structure and details. I hope this helps, -- Aymeric. > On 03 Oct 2016, at 15:21, [email protected] wrote: > > I would like to work on this ticket. As for the implementation there doesn't > seem to be much choice. The implementation with the most features is from > Bouke <https://github.com/Bouke/django-two-factor-auth>. It supports U2F, > TOTP, SMS and phone call (with Twilio by default). Beside that one only a few > packages exist: > https://github.com/gavinwahl/django-u2f > <https://github.com/gavinwahl/django-u2f>: supports only U2F, according to > the developer it's not production ready > https://bitbucket.org/psagers/django-otp/ > <https://bitbucket.org/psagers/django-otp/>: supports TOTP, HOTP > Based on the ticket description and the django developers discussion U2F and > TOTP are the most desired authentication methods. So I would like to > integrate them (orienting on Bouke > <https://github.com/Bouke/django-two-factor-auth>'s implementation) first. > And if SMS and email based authentication are also desired I would go about > them next. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/django-developers > <https://groups.google.com/group/django-developers>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/0e80fdf8-2387-4835-8ba0-2d2af01442ec%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/0e80fdf8-2387-4835-8ba0-2d2af01442ec%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0999AB8D-3CEF-494E-B9A6-A1F8E6F120EC%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
