How is make_profile rewrite working ? about django-shibboleth-remoteuser HOT 2 CLOSED

Did you ever figure this out? Your code looks fine to me so if make_profile isn't being called when a user logs in, maybe Django isn't loading the middleware correctly.

However, since make_profile is called every time a user logs in, your profile creation might be better off in the configure_user method of a custom back end so you only create a profile for the user when they first log in.
e.g.

from shibboleth.backends import ShibbolethRemoteUserBackend
from app.models.UserProfile import UserProfile

class ShibbolethRemoteUserBackendWithProfile(ShibbolethRemoteUserBackend):
    def configure_user(self, user):
        UserProfile.objects.create(user=user)
        return user

from django-shibboleth-remoteuser.

By looking on process, I saw that user was created before going in ShibbolethRemoteUserMiddleware.

This because on my Django configuration:

MIDDLEWARE_CLASSES = (
    [...]
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.auth.middleware.RemoteUserMiddleware', 
    'manage.middleware.ShibbolethRemoteUserMiddlewareWithProfile',
    [...]
)

In fact, django.contrib.auth.middleware.RemoteUserMiddleware will create user before shibbloeth middleware. In this case shibboleth middleware will ignore user and profile creation.

from django-shibboleth-remoteuser.