Bouke Haarsma
Bouke Haarsma
I've been thinking of a modular approach to django-two-factor-auth. Currently there's support for phone numbers (pluggable provider, Twillio by default), apps (QR code) and yubikeys. However there are more providers...
Historically phone/text support was not optional for this package. Over time phone/text support has increasingly been decoupled, however there are still some places where a hard dependency exists. As mention...
Good thoughts @psagers, that sounds like good improvements. Thanks for the advice on how to improve this package.
hi @mikec83, I currently have no time for maintaining this package. Also be aware that no security audit has taken place on the package's code, so YMMV.
Not sure I understand the issue here. Why would the login form's next field be empty in this case? Shouldn't it have populated from the GET parameter in this case?
I'm still not sure why the `next` parameter in the URL would be empty? Wouldn't that be the underlying problem causing this issue?
Thank you for your suggestion. It seems like a nice addition to the current call functionality.
I'm all open to this package gain support for multiple devices simultaneously. Especially useful when we would support FIDO U2F keys, where it is becoming practice to require the user...
Feel free to apply any custom styling that fits your site's layout.
Improved styling is always welcome, of course.