Django REST Framework/Django - extra user model

Question

In my project I've two different types of users:

regular Django user
worker - user which sends messages through application API and authenticates with token (basic Django rest framework token authentication)

The problem is that Token object is connected with django User object. What would be the best solution - create new user model for my worker? I don't want to extend User model because I want to have "Users" and "Workers" in my admin panel.

class Worker(models.Model):
    ip = models.GenericIPAddressField()
    created_date = models.DateTimeField()
    last_update = models.DateTimeField()

    #  but it's not the way I wish it was done:
    #  user = models.ForeignKey(User)

In general how would you solve the problem when part of users login normally with login/password and some of the users (workers) use token as an authenticating credentials ?

Could you post your models? Is worker somehow connected to the regular user model? — ilse2005
– ilse2005, Commented Mar 2, 2016 at 13:41
In fact, worker model contains only fields: ip (GenericIPAddress), created_date and last_updated_date. I tried to inherit from AbstractBaseModel but it contains a lot of unnecessary information like password etc. — hebius
– hebius, Commented Mar 2, 2016 at 13:52
I also tried to add foreign key to User in my Worker model, but then in admin panel User object must be created before creating Worker object. And Token object (from Django REST Framework) must also be created before creating worker :/ — hebius
– hebius, Commented Mar 2, 2016 at 13:54
What about inheriting from abstract base user? Or are you wanting to have this point to existing users? — Obj3ctiv3_C_88
– Obj3ctiv3_C_88, Commented Mar 2, 2016 at 14:00
Nope, I don't want to point to exisitng users. The problem is Token model from REST framework points to normal users. And if I add FK to User model in my Worker model it doesn't change anything because I still have to create normal User first, then Token and finally Worker. What I want is to have a separated Worker model and only worker objects can authenticate with token. — hebius
– hebius, Commented Mar 2, 2016 at 14:04

Obj3ctiv3_C_88 · Accepted Answer · 2016-03-02 14:05:12Z

0

Assuming you are wanting to have those same fields but want the table space to be unique you could do:

class Worker(models.AbstractBaseUser):
    ip = models.GenericIPAddressField()
    created_date = models.DateTimeField()
    last_update = models.DateTimeField()

Otherwise, if you want the worker to inherit you could do what is essentially a join by straight inheriting your auth user class by doing:

class Worker(AUTH_USER_MODEL):
    ip = models.GenericIPAddressField()
    created_date = models.DateTimeField()
    last_update = models.DateTimeField()

answered Mar 2, 2016 at 14:05

Obj3ctiv3_C_88

1,5183 gold badges17 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

hebius Over a year ago

Mmm... how about populating fields like password? It's in AbstractBaseUser class... I mean - I get this error: "You are trying to add a non-nullable field 'password' to bankworker without a default; we can't do that (the database needs something to populate existing rows)."

Obj3ctiv3_C_88 Over a year ago

You could just define a default password like an api key if a user is never going to use it or be able to access it.

hebius Over a year ago

Do I have to create manager for my custom user to set password to some dummy value?

hebius Over a year ago

Well, when I want to create new Token I still need a normal Django User object. Is there any opportunity to force TokenAuthentication point to another user model?

Collectives™ on Stack Overflow

Django REST Framework/Django - extra user model

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related