How can I prevent (massive) sharing of accounts on Django site?
First thought: to check IP's in log of each account to detect sharing and ban it, but this is pretty time-consuming
Second: to control devices per account somehow, but I have no idea how to realize that.
Suggest some ideas,
Thanks
django
add a comment |
First thought: to check IP's in log of each account to detect sharing and ban it, but this is pretty time-consuming
Second: to control devices per account somehow, but I have no idea how to realize that.
Suggest some ideas,
Thanks
django
add a comment |
First thought: to check IP's in log of each account to detect sharing and ban it, but this is pretty time-consuming
Second: to control devices per account somehow, but I have no idea how to realize that.
Suggest some ideas,
Thanks
django
First thought: to check IP's in log of each account to detect sharing and ban it, but this is pretty time-consuming
Second: to control devices per account somehow, but I have no idea how to realize that.
Suggest some ideas,
Thanks
django
django
asked Nov 12 '18 at 6:56
Дмитрий ГригоренкоДмитрий Григоренко
31
31
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
What you can do is to invalidate existing sessions when a user logs in.
So you need to look for the sessions in the project, and whenever somebody tries to log in (check for a user_logged_in event/signal globally) invalidate their existing sessions or if you want to enable only a number of concurrent sessions invalidate older existing sessions and you are done
check how to invalidate session here
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
add a comment |
Your Answer
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%2f53257200%2fhow-can-i-prevent-massive-sharing-of-accounts-on-django-site%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
What you can do is to invalidate existing sessions when a user logs in.
So you need to look for the sessions in the project, and whenever somebody tries to log in (check for a user_logged_in event/signal globally) invalidate their existing sessions or if you want to enable only a number of concurrent sessions invalidate older existing sessions and you are done
check how to invalidate session here
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
add a comment |
What you can do is to invalidate existing sessions when a user logs in.
So you need to look for the sessions in the project, and whenever somebody tries to log in (check for a user_logged_in event/signal globally) invalidate their existing sessions or if you want to enable only a number of concurrent sessions invalidate older existing sessions and you are done
check how to invalidate session here
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
add a comment |
What you can do is to invalidate existing sessions when a user logs in.
So you need to look for the sessions in the project, and whenever somebody tries to log in (check for a user_logged_in event/signal globally) invalidate their existing sessions or if you want to enable only a number of concurrent sessions invalidate older existing sessions and you are done
check how to invalidate session here
What you can do is to invalidate existing sessions when a user logs in.
So you need to look for the sessions in the project, and whenever somebody tries to log in (check for a user_logged_in event/signal globally) invalidate their existing sessions or if you want to enable only a number of concurrent sessions invalidate older existing sessions and you are done
check how to invalidate session here
answered Nov 12 '18 at 7:01
ShobiShobi
2,73811330
2,73811330
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
add a comment |
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
Good advice, thanks
– Дмитрий Григоренко
Nov 12 '18 at 7:18
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
you can accept answer though
– Shobi
Nov 12 '18 at 7:19
add a comment |
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%2f53257200%2fhow-can-i-prevent-massive-sharing-of-accounts-on-django-site%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