Last modified: 2013-02-11 09:39:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T39244, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37244 - Long lived login token is invalidated when requested in another browser
Long lived login token is invalidated when requested in another browser
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
User login and signup (Other open bugs)
1.21.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-31 12:10 UTC by Ryan Lane
Modified: 2013-02-11 09:39 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ryan Lane 2012-05-31 12:10:26 UTC
If I have two browsers open, like firefox and chrome, and I log in to MediaWiki from both, and ask to have my session remembered, the first token is invalidated by the second. So, when I close and reopen the first browser, I'm no longer logged in.
Comment 1 Tyler Romeo 2012-08-03 13:46:00 UTC
Just to clear things up, is this what you're doing:
1) Open Firefox.
2) Login to MediaWiki with "Remember me" checked.
3) Open Chrome.
4) Login to MediaWiki with "Remember me" checked.
5) Close and re-open Firefox.
Expected Result: Still logged in on Firefox.
Actual Result: No longer logged in.

I want to make sure because with those steps I cannot seem to reproduce this bug.
Comment 2 Ryan Lane 2012-12-30 21:21:45 UTC
Yes, this is the bug I'm seeing, and I'm really surprised you aren't. When you log in with chrome, it overwrites the long-lived token in your user row. I don't see how it's possible for firefox to continue to work when you close and reopen it.
Comment 3 Tyler Romeo 2013-01-25 22:19:30 UTC
Can somebody else confirm this, because I cannot reproduce it on any OS.
Comment 4 Tyler Romeo 2013-02-11 09:39:16 UTC
Going to close as WORKSFORME since I can't reproduce nor can I find any place in the code that would cause this problem. If somebody else can reproduce it can always be re-opened.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links