Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding django-stronghold #124

Closed
luzfcb opened this issue Sep 18, 2020 · 1 comment
Closed

Consider adding django-stronghold #124

luzfcb opened this issue Sep 18, 2020 · 1 comment
Labels
Done pending update Fixed in the book, will close this when we send an update to readers

Comments

@luzfcb
Copy link
Contributor

luzfcb commented Sep 18, 2020

When we develop systems and not public websites, we always want that almost every page needs authentication to be accessed, but the fact that developers can make mistakes and forget to include login_required or LoginRequiredMixin on some views can often be dangerous in terms of security.

The django-stronghold tries to solve this problem by following the same logic used in many firewalls: Everything is blocked by default (that is, required authentication) and the things that must be accessible and public must be explicitly defined.

https://github.com/mgrouchy/django-stronghold

For the project that uses django-allauth:

mgrouchy/django-stronghold#71 (comment)

Note: I don't know what level of compatibility with Django> = 3.0

@pydanny pydanny added the Done pending update Fixed in the book, will close this when we send an update to readers label Dec 15, 2020
@pydanny
Copy link
Member

pydanny commented Dec 15, 2020

🚢

@pydanny pydanny closed this as completed Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Done pending update Fixed in the book, will close this when we send an update to readers
Projects
None yet
Development

No branches or pull requests

2 participants