-
-
Notifications
You must be signed in to change notification settings - Fork 66
feat(admin): add custom admin site that reuses the allauth login #1293
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
base: master
Are you sure you want to change the base?
Conversation
Task linked: QF-6412 Use only one login page from |
@tdrivas when I ran the test locally, I couldn't manage to reproduce, any ideas what is wrong?
|
Hey, I did manage to reproduce by following the steps below:
|
@tdrivas thanks, managed to reproduce with the provided steps! |
a7eed80
to
71cf375
Compare
Do not merge, as the login page being used now is really ugly. |
efefe61
to
4f53cb7
Compare
Since login is a quite a critical part of every application, it would be great if it is always done via a single entrypoint. However, currently the login is handled either via allauth login, or via Django admin login for django admin.
Or in other words, there are
accounts/login
andadmin/login
. Suboptimal and fixed in this PR.What is more, adding a custom admin site for QFieldCloud will allow us to do other "magical" stuff.
In a follow-up PR we need to clean-up the current available configuration on the admin template and provide the same on the allauth template.
Also solves #1259