Use slumber as the loop back service. It should always be authenticated.

[jsaytoe]

If i use slumber as loop back service and i have a model that contains RemoteForeignKey that point to a model in the slumber service. Then slumber should recognize it come from itself so it should alway be authenticated.

[KayEss]

The work around for this is to create a user who is active, has the same name as the service name and whose password field contains the same values as the SECRET_KEY setting. I've not tried this, but this sort of thing should do it:

from django.contrib.auth.models import User
from django.conf import settings

User.objects.create(username=settings.SLUMBER_SERVICE, password=settings.SECRET_KEY, is_active=True)

With this user there'll be the required user in the system for Slumber to use to authenticate.