Wsrtjtyk

I would like to implement temporary users in my project. The reason is that people should be able to auth in my application via Facebook Oauth or Facebook Account Kit.

I've got 2 decisions, but each one is not ideal.

1) Create User and TemporaryUser models. The first one will have all info about regular user + unique db fields. This TemporaryUser will have only phone_number or facebook_id. Temporary user will be created on auth/ endpoint and response will have auth_token to be able perform registration later with all needed fields.

The issue is: how will I determine that user is temporary and his auth_token is legit only for registration/ endpoint?

2) Create basic User model with 2 types: regular or temporary. This model will have only general fields. Also there will be different models with OneToOne relation with User. Only Users with type regular will be able to have that instances with OneToOne relation.

The issue is: User model should have USERNAME_FIELD , REQUIRED_FIELDS to be able to login by admin panel + users with different types should have different managers.

UPDATED

class User(AbstractBaseUser, TimeStampedModel, PermissionsMixin):

    is_regular = models.BooleanField(

        default=False

    )

    id = models.CharField(

        max_length=11,

        primary_key=True,

        default=custom_uuid,

        editable=False

    )

    phone_number = PhoneNumberField(

        null=True

    )

    facebook_id = models.CharField(

        max_length=255,

        null=True

    )



    objects = UserManager()

    USERNAME_FIELD = 'phone_number'

    REQUIRED_FIELDS = 

From discussion, there are many ways to tackle this issue. But using two different models for authentication purpose is a bad idea. Because Django Auth was designed assuming one User Model.

This is how I would have approached:

1. Rather than using facebook_id, I would have stored email from facebook's graph API. While creating the password, I would have used an unique UUID.


2. Put a temporary flag(a Model Boolean Field) to track if the user is registered through social media. So when he tries to login to normal path or registration, I would know that he does not have a password, so I would send him to reset his password. After successful reset password, I would have removed that temporary flag.


3. 
   

   Other information which are absolute necessary, I would have used a separate model to store them. For example:

   
   
   

   class Profile(models.Model):
   
       ...
   
       phone_number = models.CharField(max_length=30)
   
       user = models.OneToOneField(settings.AUTH_USER_MODEL)
   
   

   
   
   

   And checked with login that if the User has a profile or not:

   
   
   

   if not hasattr(user, 'profile'):
   
        # redirect to more information page
   
   

   
   



4. For other permissions for accessing admin site should be restricted creation through normal registration or social registration. For these users, those fields(is_staff, is_superuser etc should be False by default. For admin user creation, you can use createsuperuser command. For staff users, you can later assign a normal user to staff by making the is_staff flag True from adminsite or Django Shell.

Update(from comments...)

You can use custom Backend for authenticating facebook user:

from django.contrib.auth.backends import ModelBackend

from django.db.models import Q



class CustomModelbackend(ModelBackend):

    def authenticate(self, phone_no=None, password=None, facebook_id=None, **kwargs):

        # Override

        UserModel = User

        try:

            user = UserModel.objects.get(Q(phone_no=phone_no) | Q(facebook_id=facebook_id))

            if password and user.check_password(password):   

                return user

            elif facebook_id:

                return user

        except Exception as e:

            # log exception

and add it to AUTHENTICATION_BACKENDS in settings.py:

AUTHENTICATION_BACKENDS = ['path.to.custom_backend.CustomBackend']

and call authenticate method like this:

 authenticate(phone_no=phone_number, password=password)  # for normal auth

 authenticate(facebook_id=facebook_id)  # for social auth

But you can't make your phone_no unique as there is chance of the phone_no being empty for social login, but you can put it in USERNAME_FIELD. So you will see warnings when you run django developer server(runserver command)

Update (2)

You can try like this:

NORMAL_USER = "N"

OAUTH_USER = "O"

AT_USER = "A"

USER_TYPES=(

    (NORMAL_USER, 'Normal User'),

    (OAUTH_USER, 'Oauth User'),

    (AT_USER, 'Account Toolkit User')

)



class User(...):

    username = models.CharField(max_length=255, default=uuid.uuid4, unique=True)  # it might be unnecessary

    account_type = models.CharField(max_length=2, choices = USER_TYPES, default=NORMAL_USER)

    identifier = models.CharField(max_length=255)

    ...



    class Meta:

        unique_togather = ('account_type', 'identifier',)





# for Oauth Creation



User.objects.create(account_type=OAUTH_USER, identifier=facebook_id)  # or email



# for Toolkit Creation



User.objects.create(account_type=AT_USER, identifier=phone_number)



# For normal User

User.objects.create(identifier=username, username=username)



#backend, and does not need to use ModelBackend, it will work with adminsite

class CustomBackend(...):

    def authenticate(self, **kwargs):

        try:

            identifier= kwargs.get('username')

            password=kwargs.get('password')

            account_type=kwargs.get('account_type', NORMAL_USER)

            user = User.objects.get(identifier=identifier, account_type=account_type)

            if user.check_password(password):

                return user

        except Exception:

            # log exception



# authentication

from django.contrib.auth import authenticate

user = authenticate(username=identifier, password=password, account_type=OAUTH_USER)