There is no special reason as to why I chose a boilerplate and not a pluggable app. Creating a boilerplate for the task I've been doing a lot came off straightforward.
And I've not seen django-mfa before, but looking at it now, it says that it allows users to authenticate through text message(SMS) or using a token generator app. Does it allow email authentication as well? and also is it compatible with Django version 4?
Can't say, I've only bookmarked as a to-do, to explore using it on my site when I need user logins and such more than at present (I'm still on an internal alpha). Which is why I have an eye open for solutions in this space. Surely the dream of a Django site admin is to have login systems like the big players do, MFA and password recovery, and social media authentication via Google, FB, GitHub etc.
Interesting. But why a boilerplate, Why not a pluggable app, that Django supports so well? And what are the shortcomings of django-mfa that you see?
pypi.org/project/django-mfa/
Hi Bernd, Thanks for the feeback :)
There is no special reason as to why I chose a boilerplate and not a pluggable app. Creating a boilerplate for the task I've been doing a lot came off straightforward.
And I've not seen django-mfa before, but looking at it now, it says that it allows users to authenticate through text message(SMS) or using a token generator app. Does it allow email authentication as well? and also is it compatible with Django version 4?
Can't say, I've only bookmarked as a to-do, to explore using it on my site when I need user logins and such more than at present (I'm still on an internal alpha). Which is why I have an eye open for solutions in this space. Surely the dream of a Django site admin is to have login systems like the big players do, MFA and password recovery, and social media authentication via Google, FB, GitHub etc.
Agree!