thanx for the solution – it is exactly what i was seraching for – but somehow it is not working.

When trying to log in the admin site for example, i get the

"ImproperlyConfigured at /admin/

Module "mysite.auth_backends" does not define a "CustomUserModelBackend" authentication backend

The auth_backends.py is exactly the same you showed, and the CustomUser is just different in it’s fields (not timezone for example)

My Settings is configured like this:

AUTH_PROFILE_MODULE = 'mysite..user_ext'

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

Any ideas? I want to feel the magic pony ;)

Regards,
Kalle

thank you for this article.

Unfortunately i’m having an issue; i’m able to create a CustomUser through the admin interface (like described in comment #8).
But the CustomUsers will appears in admin/auth/user/ (without the custom fields) and nothing will appear in admin/myapp/customuser/.

Is there a clean way to fully add/list/edit extended users through the admin interface or must i make my own admin interface?

When I create a foreign key to the new CustomUser class and specify “to_field = ‘username’” it works fine with validation and saving but the moment you try and do a order_by on the new model which references a field in the User model it fails with customuser__username field not found.

Example:

class CustomUser(User):
    ......

class X(models.Model):
    added_by = models.ForeignKey(CustomUser, to_field = 'username')

X.objects.all().order_by('added_by__last_name)

I use auto complete fields in my forms that use the username as a value so if I don’t specify to_field in my model the validation will fail as it’s expecting the CustomUser.id.

Maybe there is a way to tell the ModelForm to validate using the username?

delimiter //
create trigger trigger_custom_user
after insert on auth_user
for each row
begin
insert into myapp_customuser (user_ptr_id) values(NEW.id);
//

It’s at the sql level and therefore not ideal, but it works.

http://steps.ucdavis.edu/People/jbremson/extending-the-user-model-in-django