Custom users not superusers from django
I started with Django Rest Framework official tutorial (https://www.django-rest-framework.org/tutorial/4-authentication-and-permissions/) earlier today,
and I have a question in the authentication and permissions section,
If I want to have custom users table, not the default superuser created by Django, is there any feature in DRF that help me with this requirement ??
and if there isn't, is it a good way to use the python manage.py createsuperuser to create a whole table of users that may contain 100 user ??
Im new to python, django, and DRF
so thanks for any help.
python django django-rest-framework
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
add a comment |
I started with Django Rest Framework official tutorial (https://www.django-rest-framework.org/tutorial/4-authentication-and-permissions/) earlier today,
and I have a question in the authentication and permissions section,
If I want to have custom users table, not the default superuser created by Django, is there any feature in DRF that help me with this requirement ??
and if there isn't, is it a good way to use the python manage.py createsuperuser to create a whole table of users that may contain 100 user ??
Im new to python, django, and DRF
so thanks for any help.
python django django-rest-framework
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05
add a comment |
I started with Django Rest Framework official tutorial (https://www.django-rest-framework.org/tutorial/4-authentication-and-permissions/) earlier today,
and I have a question in the authentication and permissions section,
If I want to have custom users table, not the default superuser created by Django, is there any feature in DRF that help me with this requirement ??
and if there isn't, is it a good way to use the python manage.py createsuperuser to create a whole table of users that may contain 100 user ??
Im new to python, django, and DRF
so thanks for any help.
python django django-rest-framework
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
I started with Django Rest Framework official tutorial (https://www.django-rest-framework.org/tutorial/4-authentication-and-permissions/) earlier today,
and I have a question in the authentication and permissions section,
If I want to have custom users table, not the default superuser created by Django, is there any feature in DRF that help me with this requirement ??
and if there isn't, is it a good way to use the python manage.py createsuperuser to create a whole table of users that may contain 100 user ??
Im new to python, django, and DRF
so thanks for any help.
python django django-rest-framework
python django django-rest-framework
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
asked Nov 13 '18 at 17:22
MhmdRizkMhmdRizk
523414
523414
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05
add a comment |
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05
add a comment |
0
active
oldest
votes
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53286447%2fcustom-users-not-superusers-from-django%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53286447%2fcustom-users-not-superusers-from-django%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Your question is not clear. Django includes a User model and you can create any number of users, either normal or superuser.
– Daniel Roseman
Nov 13 '18 at 17:23
what I mean is that I need a customer model ,and the customer will technically be a user which can login , logout , and perform some of the APIs I’m developing, is it technically right to create this customer using the user model , or its better to create a custom user model ?
– MhmdRizk
Nov 13 '18 at 17:35
It is not only technically right it is absolutely the correct thing to do.
– Daniel Roseman
Nov 13 '18 at 17:41
You should read here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… and here: docs.djangoproject.com/en/2.1/topics/auth/customizing/… This are basically two patterns that are proposed by django developers. If you will keep interfaces (inherit from one of the django abstract users models) drf - will have no problem to handle that.
– opalczynski
Nov 13 '18 at 19:05