django-authentication

How to get the currently logged-in user's id? in models.py : class Game(models.model): name = models.CharField(max_length=255) owner = models.ForeignKey(User, related_name='game_user', verbose_name='Owner') in views.py : gta = Game.objects.create(name="gta", owner=?) K Z First make sure you have SessionMiddleware and AuthenticationMiddleware middlewares added to your MIDDLEWARE_CLASSES setting. The current user is in request object, you can get it by: def sample_view(request): current_user = request.user print current_user.id request.user will give you a User object representing the currently

In django/contrib/auth/views.py there is the definition of the logout view : def logout(request, next_page=None, template_name='registration/logged_out.html', redirect_field_name=REDIRECT_FIELD_NAME, current_app=None, extra_context=None): I would like to add extra_context to get rid of the 'Logged out' title that appear when I log off so I'm trying this in my url confs : (r'^accounts/logout/$', logout(extra_context={'title':'something else'}) ), but then I get this error : logout() takes at least 1 non-keyword argument (0 given) what I'm doing wrong? ps: when I do (r'^accounts/logout/$',

After connecting an account with a social app using django-allauth the user is redirected to accounts/social/connections . How can I change this behavior? pennersr If the user is adding more social accounts to his existing (local) account, then the most logical default would be indeed to redirect to the social account connections management screen. However, you can easily override the default by passing along a next parameter. Have a look here: https://github.com/pennersr/django-allauth/blob/master/allauth/socialaccount/helpers.py#L125 You'll see that the next parameter is checked, falling

In another post , I mentioned that I was trying to use allauth's email_confirmed signal to change the is_active field on the confirmed user to true. However, the following code gave me the exception "User matching query does not exist." from allauth.account.signals import email_confirmed from django.dispatch import receiver from django.contrib.auth.models import User @receiver(email_confirmed) def email_confirmed_(request, email_address, **kwargs): user = User.objects.get(email=email_address) user.is_active = True user.save() I tried to re-work this, and still got a similar exception,

I am rewriting a legacy application that has a database for each customer. Each customer has its own authentication and user set. Thus, I'll need a custom authentication backend because django's auth is set to only use default. I have written middleware that examines the url upon every request and extracts information there to set a database_name on the request. If I had access to the request during processing of my custom authencation backend, I could easily perform database calls as user = User.objects.using(request.db).get(username=username) However, I see no easy way to accomplish this. I