django-authentication

Is it possible to prevent account creation under certain circumstances in allauth, preferably using the pre_social_login signal? With the current development branch you can easily do this. In your settings: SOCIALACCOUNT_ADAPTER = 'my.adapter.MySocialAccountAdapter' Then use this adapter.py: from django.http import HttpResponse from allauth.socialaccount.adapter import DefaultSocialAccountAdapter from allauth.exceptions import ImmediateHttpResponse class MySocialAccountAdapter(DefaultSocialAccountAdapter): def pre_social_login(self, request, sociallogin): raise ImmediateHttpResponse

I have two very related sites, would like users using each to only to have to login once. Either two apps under one django project serving different domains? Is this possible? or is there some way to share the authentication between two separate django projects? Cheers Asim There are lots of ways you can solve this problem. Here are some things to look into. I'm ordering based on my preference, if you've got some questions, or more specificity to your question, it could change. Use the same database. Make one site an OpenID provider for the other Use Django's MultiDB functionality (NOTE! You

I'm using the default change password mechanism provided by django. I'm using post_change_redirect to have the submitted form go straight back to my settings page, however I'd like to show a message to reassure the user that the operation has been successful. How can I detect whether I'm arriving in my settings view as the result of a successful password change, and add a message to that effect? I wouldn't recommend checking in the settings view whether a user has arrived via a password change. I think that ideally, all of the logic for password changes is contained in the same place. This

I have enabled user authentication with DRF using TokenAuthentication REST_FRAMEWORK = { 'DEFAULT_AUTHENTICATION_CLASSES': ( 'rest_framework.authentication.TokenAuthentication', 'rest_framework.authentication.SessionAuthentication' ), 'DEFAULT_MODEL_SERIALIZER_CLASS': 'rest_framework.serializers.ModelSerializer', 'DEFAULT_PERMISSION_CLASSES': ( 'rest_framework.permissions.AllowAny', ), #'EXCEPTION_HANDLER': 'apps.core.exceptions.custom_exception_handler' } I have the following model: class Device(CreationModificationMixin): """ Contains devices (WW controllers). A device may be associated with

When I run my django test I get following errors, that are outside of my test suite: ====================================================================== ERROR: test_known_user (django.contrib.auth.tests.remote_user.RemoteUserCustomTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/django/contrib/auth/tests/remote_user.py", line 160, in test_known_user super(RemoteUserCustomTest, self).test_known_user() File "/usr/lib/pymodules/python2.6/django/contrib/auth/tests/remote_user.py", line 67, in test

I want to serve a Django application that serves multiple web sites by single database but different user sets. Think like a blog application, it will be used by several domains with different themes, but use same database by adding a site field to models. I use Django's SitesFramework for that job. But the problem is, I couldn't separate user models for different sites. I want to use same user model with a site field and email field that unique per site. I tried to extend AbstractUser model like that: from django.contrib.auth.models import AbstractUser from django.contrib.sites.models import