Page MenuHomePhabricator

SUL has stopped working for at least some users
Closed, ResolvedPublic

Description

Multiple users are reporting that SUL no longer works properly for them. This seems to vary per-project, or at least be non-deterministic; we have users reporting that, for example, signing in on Wikiversity made SUL work but trying to sign in on Wiktionary made it fail. Thread at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Strange_global_login_behavior_and_bugs_with_Gecko_based_browsers

(Lego, pointing you at this because I have literally no idea who else to point it to. I imagine you do ;p)

Event Timeline

Ironholds assigned this task to Legoktm.
Ironholds raised the priority of this task from to Unbreak Now!.
Ironholds updated the task description. (Show Details)
Ironholds subscribed.
Ironholds set Security to None.

Since we changed the cache key, I wonder if this is due to wikis being on different branches. The steps to reproduce (from en:WP:VPT) line up properly with our different deployment groups...

  1. signed into Wikipedia and noticed I wasn't signed into any other project;
  2. signed in on Wiktionary and found I was logged into Commons, Meta, and Wikidata;
  3. signed out on Wikipedia, and found I wasn't signed out of any other project;
  4. signed out on Wiktionary, and found I was signed out of all projects

That said I couldn't reproduce using my "Lego-test" account in Firefox.

Few hours ago, as referred in Village pump, I also had problems with logins. My account (which was recently created) had no problems at the time I created, I was able to log in at Commons. Then later, whenever I tried to log in, only the home wiki (Wikipedia) could log me in, but the other projects gave me this output when trying to log in:

Login error
Incorrect password or confirmation code entered. Please try again.

Now I reseted the password and I see no problems so far (too soon to tell). I removed the character 'ç' from the password hoping that it would fix my problem, if the code was accepting only ASCII characters as password.

The tested browsers were:

  1. Google Chrome 44 (stable) and Microsoft Edge on Windows 10
  2. Google Chrome 44 (stable) and Firefox 39 (stable) on Android 5.1.1

Now I reseted the password and I see no problems so far (too soon to tell). I removed the character 'ç' from the password hoping that it would fix my problem, if the code was accepting only ASCII characters as password.

Which struck me as really odd, and potentially a separate issue. I opened T108221 to track that.

Tgr subscribed.

Given the Unbreak Now! priority and the conspicuous lack of pitchforks, I am assuming this is fixed.