1

I'd like to extend the User model, so I can put in some extra fields and functions (not only fields, keep in mind, or else (well, still) I could use get_profile(), which I think is ugly).

Also I would like to use that new extended User model in request.user, like this:

Extended User model:

# imports etc

class CustomUser(User):
    extra_field = ...

    def extra_function(self):
        ...

        return ...

Example usage view:

# imports etc

def extra_function_view(request):
    print request.user.username
    print request.user.extra_field

    request.user.extra_function()

    return HttpResponse( ... )

The above code obviously doesn't work, because extra_field and extra_function are not in the User model.

Now I found a method to accomplish this, using an authentication backend, which is kinda complex, and which I couldn't get to work in Django 1.2.3.

AUTHENTICATION_BACKENDS = (
    'myproject.auth_backends.CustomUserModelBackend',
)
...

CUSTOM_USER_MODEL = 'accounts.CustomUser'

Further more tried some other methods, like using signals, which didn't work. To me, the only solution seems to adjust the User model within Django (which isn't an elegant solution, adjusting Django's source code, but is code-wise a neat solution).

So I'm looking for a solution for this.. has anyone done this before?

Thanks for now

Stefan

Boemknaldaarstaatieal
  • 21
  • 2

1 Answers1

2

You're on the right track with adjusting the Authentication Backend.

Authentication backends can be pretty simple, here is a snip of ours we use in our project.

class LocalAccount(object):
    def authenticate(self, system=None, username=None, password=None):
        try:
            user = User.objects.get(system=system, alias=username)
            if user.check_password(password):
                return user
        except User.DoesNotExist:
            return None

    def get_user(self, user_id):
        'returns user'

    def get_all_permissions(self, user_obj):
        'returns user permissions'

    def has_perm(self, user_obj, perm):
        'verifies permission, remember you can hardcode these'

    def get_group_permissions(self, user_obj):
        return set() #We don't use this

    def has_module_perms(self, user_obj, app_label):
        return False

This allows you to return whatever user model you wish to return. As long as your user model is basically like Django's user model you won't run into any issues.

Also keep in mind that extending user and including the application will cause both the Django User model and your own User model to be in the database with model inheritance. Your best option is to copy the Django User model and alter it. For our project we don't even include 'auth' in the installed apps setting.

The concept here is Python duck typing. As long as the User model that you create has the same interface that Django is looking for (methods, fields) it doesn't matter if it's actually the User class it specified.

Xealot
  • 1,659
  • 14
  • 26
  • Similar to what I've done, but I live with the model inheritance. – Ignacio Vazquez-Abrams Nov 30 '10 at 14:01
  • Completely understandable and valid, it annoyed me to no end though :) – Xealot Nov 30 '10 at 14:08
  • So what are you saying now? That I need to go for the authentication backend of for editing the original Django User model? If so, copying the contrib.auth directory into my own project is enough, and understandable for Django when adding it to my settings? – Boemknaldaarstaatieal Dec 01 '10 at 09:55
  • You just need a User model that will subscribe to the interface of Djangos own User model. After that it's just a matter of your authentication backend returning YOUR User model instead of Djangos. – Xealot Dec 01 '10 at 20:42