How to use different session id for same user across different django project with same database
I have 2 Django projects running on different domains. Both are using the same database and the same models. One project is in 2.7 and another project is in 3.7.
When user login into one domain, it logs out the user from other domain.
I have login in chrome using one domain. It works and 1 entries exists in django session. but when i login into chrome using another domain. Still 1 previous sessionid exists in django_sessions but when i refresh first domain page, it log me out from first domain and now django_sessions does not have previous first domain sessionid in db.
How can i restrict him to not logging the user out from one domain on login into another domain?
django-users django-middleware django-sessions session-management
add a comment |
I have 2 Django projects running on different domains. Both are using the same database and the same models. One project is in 2.7 and another project is in 3.7.
When user login into one domain, it logs out the user from other domain.
I have login in chrome using one domain. It works and 1 entries exists in django session. but when i login into chrome using another domain. Still 1 previous sessionid exists in django_sessions but when i refresh first domain page, it log me out from first domain and now django_sessions does not have previous first domain sessionid in db.
How can i restrict him to not logging the user out from one domain on login into another domain?
django-users django-middleware django-sessions session-management
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10
add a comment |
I have 2 Django projects running on different domains. Both are using the same database and the same models. One project is in 2.7 and another project is in 3.7.
When user login into one domain, it logs out the user from other domain.
I have login in chrome using one domain. It works and 1 entries exists in django session. but when i login into chrome using another domain. Still 1 previous sessionid exists in django_sessions but when i refresh first domain page, it log me out from first domain and now django_sessions does not have previous first domain sessionid in db.
How can i restrict him to not logging the user out from one domain on login into another domain?
django-users django-middleware django-sessions session-management
I have 2 Django projects running on different domains. Both are using the same database and the same models. One project is in 2.7 and another project is in 3.7.
When user login into one domain, it logs out the user from other domain.
I have login in chrome using one domain. It works and 1 entries exists in django session. but when i login into chrome using another domain. Still 1 previous sessionid exists in django_sessions but when i refresh first domain page, it log me out from first domain and now django_sessions does not have previous first domain sessionid in db.
How can i restrict him to not logging the user out from one domain on login into another domain?
django-users django-middleware django-sessions session-management
django-users django-middleware django-sessions session-management
edited Jan 3 at 9:05
Ehsaan Israr
asked Jan 1 at 10:46


Ehsaan IsrarEhsaan Israr
531111
531111
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10
add a comment |
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10
add a comment |
0
active
oldest
votes
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%2f53994828%2fhow-to-use-different-session-id-for-same-user-across-different-django-project-wi%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%2f53994828%2fhow-to-use-different-session-id-for-same-user-across-different-django-project-wi%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
By default, sessions are stored in the database - that could be causing the conflict between the two apps. Try switching to a different sessions storage technique - docs.djangoproject.com/en/2.1/topics/http/sessions.
– Wiggy A.
Jan 1 at 10:51
Entries from django_session table are not deleting on login. Entries from django_session are deleting after login on page refresh.
– Ehsaan Israr
Jan 1 at 11:10