I have a model with a created_by field that is linked to the standard Django User model.  I need to automatically populate this with the ID of the current User when the model is saved.  I can&#39;t do this at the Admin layer, as most parts of the site will not use the built-in Admin.  Can anyone advise on how I should go about this?

Django: Populate user ID when saving a model

In order to sign users in after registering them, I manually set the user.backend property.  It normally works in my views.  In this instance, I&#39;m trying to register the user via AJAX.  It is raising an AttributeError. 

Here is my code:


          
     def register_async(request):
	    if request.method==&#39;POST&#39;:
			
		userform=MyUserCreationForm(request.POST)
		if userform.is_valid():
			#username of &lt;30 char is required by Django User model.  I&#39;m storing username as a hash of user email 
					
			user=userform.save(commit=False)
			user.username=hash(user.email)
			user.backend=&#39;django.contrib.auth.backends.ModelBackend&#39;
			user.save()
			
			
			auth.login(request,user)
			user_status=1
			user_fname=user.first_name
			user_data=[{&#39;user_status&#39;:user_status, &#39;user_fname&#39;:user_fname}]
			json_data=json.dumps(user_data)
			response=HttpResponse()
			response[&#39;Content-Type&#39;]=&quot;text/javascript&quot;
			response.write(json_data)
			return response	

		else:
			user_data=[{&#39;user_status&#39;:&quot;0&quot;}]
			json_data=json.dumps(user_data)
			response=HttpResponse()
			response[&#39;Content-Type&#39;]=&quot;text/javascript&quot;
			response.write(json_data)
			return response	
	else:
		return HttpResponse()


EDIT-- HERE&#39;S THE AJAX. IT SEEMS PRETTY STANDARD

         //ajax registration.  
	$(&#39;input#register_submit&#39;).click(function(event){
		$(this).attr(&#39;disabled&#39;,&#39;disabled&#39;);
		$(&#39;&lt;div class=&quot;register-animation&quot;&gt;&lt;img src=&quot;{{site}}media/ajax-loader3.gif&quot;/&gt;&lt;/div&gt;&#39;).appendTo(&#39;#register_modal_btn&#39;);
		
		$.post(&quot;/register/&quot;, $(&#39;div#register_side form&#39;).serialize(), 
			function(data){
				$.each(data,function(){
				if(this.user_status==1){
					$(&#39;.register-animation&#39;).remove();
					$(&#39;.right_section .top&#39;).html(&#39;&lt;ul&gt;&lt;li class=&quot;sep_nav&quot;&gt;Hi, &#39;+ this.user_fname + &#39;&lt;/li&gt;&lt;li class=&quot;sep+nav&quot;&gt;&lt;a href=&quot;http://nabshack.com/logout/&quot;&gt;Log Out&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;refar_friend&quot;&gt;&lt;a href=&quot;http://nabshack.com/referral/&quot;&gt;Refer a friend and get $50&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&#39;);
					$(&#39;#post_login_modal&#39;).dialog(&quot;close&quot;);
		
					$(&#39;a.login&#39;).unbind(&#39;click&#39;);
					$(&#39;li a.account&#39;).unbind(&#39;click&#39;);
		
				}		
				else{
				$(&#39;input#register_submit&#39;).removeAttr(&#39;disabled&#39;);
				$(&#39;.register-animation&#39;).remove();
				window.location=&#39;{{site}}register&#39;;
				}
				
			});
		},&#39;json&#39;);
		return false;
		event.stopPropagation();
	});


Pretty much this exact code works in non-ajax views for me.  What gives?

Thanks

Django-AttributeError &#39;User&#39; object has no attribute &#39;backend&#39; (But....it does?)

We have a Django application that requires a specific level of password complexity. We currently enforce this via client-side JavaScript which can easily be defeated by someone who is appropriately motivated.

I cannot seem to find any specific information about setting up server-side password strength validation using the django contrib built in views. Before I go about re-inventing the wheel, is there a proper way to handle this requirement?



Enforcing password strength requirements with django.contrib.auth.views.password_change

I want users on the site to be able to download files whose paths are obscured so they cannot be directly downloaded.

For instance, I&#39;d like the URL to be something like this: `http://example.com/download/?f=somefile.txt`

And on the server, I know that all downloadable files reside in the folder `/home/user/files/`.

Is there a way to make Django serve that file for download as opposed to trying to find a URL and View to display it?

Having Django serve downloadable files

I created a custom group in Django&#39;s admin site.

In my code, I want to check if a user is in this group. How do I do that?

In Django, how do I check if a user is in a certain group?

I&#39;m having a bit of trouble understanding how the new CBVs work. My question is this, I need to require login in all the views, and in some of them, specific permissions. In function-based views I do that with @permission_required() and the login_required attribute in the view, but I don&#39;t know how to do this on the new views. Is there some section in the django docs explaining this? I didn&#39;t found anything. What is wrong in my code?

I tried to use the @method_decorator but it replies &quot;**TypeError at /spaces/prueba/ _wrapped_view() takes at least 1 argument (0 given)**&quot;

Here is the code (GPL):

    from django.utils.decorators import method_decorator
    from django.contrib.auth.decorators import login_required, permission_required
    
    class ViewSpaceIndex(DetailView):
    
        &quot;&quot;&quot;
        Show the index page of a space. Get various extra contexts to get the
        information for that space.
        
        The get_object method searches in the user &#39;spaces&#39; field if the current
        space is allowed, if not, he is redirected to a &#39;nor allowed&#39; page. 
        &quot;&quot;&quot;
        context_object_name = &#39;get_place&#39;
        template_name = &#39;spaces/space_index.html&#39;
        
        @method_decorator(login_required)
        def get_object(self):
            space_name = self.kwargs[&#39;space_name&#39;]
            
            for i in self.request.user.profile.spaces.all():
                if i.url == space_name:
                    return get_object_or_404(Space, url = space_name)
    
            self.template_name = &#39;not_allowed.html&#39;
            return get_object_or_404(Space, url = space_name)
    
        # Get extra context data
        def get_context_data(self, **kwargs):
            context = super(ViewSpaceIndex, self).get_context_data(**kwargs)
            place = get_object_or_404(Space, url=self.kwargs[&#39;space_name&#39;])
            context[&#39;entities&#39;] = Entity.objects.filter(space=place.id)
            context[&#39;documents&#39;] = Document.objects.filter(space=place.id)
            context[&#39;proposals&#39;] = Proposal.objects.filter(space=place.id).order_by(&#39;-pub_date&#39;)
            context[&#39;publication&#39;] = Post.objects.filter(post_space=place.id).order_by(&#39;-post_pubdate&#39;)
            return context

How to use permission_required decorators on django class-based views

How to get the currently logged-in user&#39;s id?

in `models.py`:

    class Game(models.model):
        name = models.CharField(max_length=255)
        owner = models.ForeignKey(User, related_name=&#39;game_user&#39;, verbose_name=&#39;Owner&#39;)
    

in `views.py`:

    gta = Game.objects.create(name=&quot;gta&quot;, owner=?)

How to get the currently logged in user&#39;s user id in Django?

Can I use the Auth application&#39;s permission checking inside a template in Django? (I want to display a simple form at the end of the template for privileged users)

And more importantly, should I do it at all or is this no the &quot;Django way&quot;?

Check permission inside a template in Django

What&#39;s the best way to extend the User model (bundled with Django&#39;s authentication app) with custom fields? I would also possibly like to use the email as the username (for authentication purposes).

I&#39;ve already seen a [few][1] [ways][2] to do it, but can&#39;t decide on which one is the best.


  [1]: http://scottbarnham.com/blog/2008/08/21/extending-the-django-user-model-with-inheritance/
  [2]: http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/

Extending the User model with custom fields in Django

I have created users for my unit tests in two ways: 

1) Create a fixture for &quot;auth.user&quot; that looks roughly like this: 

        { 
            &quot;pk&quot;: 1, 
            &quot;model&quot;: &quot;auth.user&quot;, 
            &quot;fields&quot;: { 
                &quot;username&quot;: &quot;homer&quot;, 
                &quot;is_active&quot;: 1, 
                &quot;password&quot;: 
    &quot;sha1$72cd3$4935449e2cd7efb8b3723fb9958fe3bb100a30f2&quot;, 
                ... 
            } 
        }

 
I&#39;ve left out the seemingly unimportant parts. 

2) Use &#39;create_user&#39; in the setUp function (although I&#39;d rather keep 
everything in my fixtures class): 

    def setUp(self): 
           User.objects.create_user(&#39;homer&#39;, &#39;ho...@simpson.net&#39;, &#39;simpson&#39;) 

Note that the password is simpson in both cases. 

I&#39;ve verified that this info is correctly being loaded into the test database time and time again. I can grab the User object using User.objects.get. I can verify the password is correct using &#39;check_password.&#39; The user is active. 

Yet, invariably, self.client.login(username=&#39;homer&#39;, password=&#39;simpson&#39;) FAILS. I&#39;m baffled as to why. I think I&#39;ve read every single Internet discussion pertaining to this. Can anybody help? 

The login code in my unit test looks like this: 
                
        login = self.client.login(username=&#39;homer&#39;, password=&#39;simpson&#39;) 
        self.assertTrue(login) 

Thanks.

Django&#39;s self.client.login(...) does not work in unit tests

From the [Django.Contrib.Auth docs][1]:

&gt; **Extending Django’s default User**
&gt; If you’re entirely happy with Django’s User model and you just want to add some additional profile information, you can simply subclass `django.contrib.auth.models.AbstractUser` and add your custom profile fields. This class provides the full implementation of the default User as an abstract model.


Said and done. I created a new model like below:

    class MyUser(AbstractUser):
      some_extra_data = models.CharField(max_length=100, blank=True)

This shows up in admin almost like Django&#39;s standard `User`. However, the most important difference in admin is that the password-(re)set field is not present, but a normal CharField is displayed instead. Do I really have to override stuff in the admin-config to get this to work? If so, how can I do that in somewhat DRY way (i.e. without copying stuff from the Django source... eww...)?

  [1]: https://docs.djangoproject.com/en/dev/topics/auth/customizing/#extending-django-s-default-user


Using Django auth UserAdmin for a custom user model

In my Django app under certain conditions I want to be able to force users to log out by a username. Not necessarily the current user who is logged in, but another user. So, the request method in my view doesn&#39;t have any session information about the user that I want to logout.

I am familiar with django.auth and with auth. logout method, but it takes _request_ as an argument. Is there a &quot;Django-way&quot; to log the user out if all I have is the username? Or do I have to roll my own logout SQL?


How to force a user logout in Django?

I hope you can help me figure the best way to implement a manual (server-side initiated) login *without* using the password. Let me explain the workflow:  

- User registers
- Thank you! An email with an activation link has been sent blablabla
- (Account now exists but is marked not enabled)
- User opens email, clicks link
- (Account is enabled)
- Thank you! You can now use the site

What I&#39;m trying to do is log in the user after he has clicked the email link so he can start using the website right away.

I can&#39;t use his password since it&#39;s encrypted in the DB, is the only option writing a custom authentication backend?

Manually logging in a user without password

I&#39;m creating a few users by default in my `fixtures/initial_data.json` so as to have some testing &quot;subjects.&quot; The problem I&#39;m experiencing is password generation. I could set the password in the &#39;fields&#39;, but that won&#39;t generate a hashed password:

    [
        { &quot;model&quot;: &quot;auth.user&quot;,
            &quot;pk&quot;: 1,
            &quot;fields&quot;: {
                &quot;username&quot;: &quot;user1&quot;,
                &quot;password&quot;: &quot;password&quot;
            }
        }
    ]

I need a way to generate the user&#39;s password. Do I have to do this manually and generate a string like `{hash_method}${salt}${hashed_password}` like Django does?  

Users in initial data fixture

Is there anything wrong with running alter table on `auth_user` to make `username` be `varchar(75)` so it can fit an email? What does that break if anything?

If you were to change `auth_user.username` to be `varchar(75)` where would you need to modify django? Is it simply a matter of changing 30 to 75 in the source code?

    username = models.CharField(_(&#39;username&#39;), max_length=30, unique=True, help_text=_(&quot;Required. 30 characters or fewer. Letters, numbers and @/./+/-/_ characters&quot;))

Or is there other validation on this field that would have to be changed or any other repercussions to doing so?

See comment discussion with bartek below regarding the reason for doing it.

**Edit**: Looking back on this after many months. For anyone who doesn&#39;t know the premise: Some apps don&#39;t have a requirement or desire to use a username, they use only email for registration &amp; auth. Unfortunately in django auth.contrib, username is required. You could start putting emails in the username field, but the field is only 30 char and emails may be long in the real world. Potentially even longer than the 75 char suggested here, but 75 char accommodates most sane email addresses. The question is aimed at this situation, as encountered by email-auth-based applications.

Can django&#39;s auth_user.username be varchar(75)? How could that be done?

What&#39;s the best way to get user information from a django template?

For example, if I just want to:

1. If the user is logged in, display &quot;Welcome [username]&quot;
2. Otherwise, display the login button.

I&#39;m using django-registration/authentication

All Django Authentication Solutions on Gang of Coders

Total of 16 Django Authentication Solutions

Django: Populate user ID when saving a model

Django-AttributeError 'User' object has no attribute 'backend' (But....it does?)