Closed
Bug 1247391
Opened 8 years ago
Closed 8 years ago
[Persona] Unable to verify Persona login using Firefox Browser
Categories
(Cloud Services :: Server: Identity, defect)
Cloud Services
Server: Identity
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: liz, Unassigned)
Details
Attachments
(3 files)
Firefox 44.0.1 fails - Error message when trying to log into either air.mozilla.org or moderator tool. This works using Chrome. Attached is a screenshot of the error console. We tried turning tracking protection off but that didn't seem to fix the issue.
Reporter | ||
Comment 1•8 years ago
|
||
Here's a screenshot of the error message
Updated•8 years ago
|
Component: General → Untriaged
Updated•8 years ago
|
Component: Untriaged → air.mozilla.com
Product: Firefox → Websites
Reporter | ||
Comment 2•8 years ago
|
||
I just discovered that I get the same can't verify message on mozillians.org.
Reporter | ||
Comment 3•8 years ago
|
||
Hi. I'm still having this problem. I can't log into Air Mozilla, the Moderator Tool, or mozillians.org using Firefox, so it seems like a Persona related issue. I can log into all 3 services in Chrome. It seems unlikely I'm the only one. If someone could figure out what's going on, I'd really appreciate it. Thanks.
Updated•8 years ago
|
Component: air.mozilla.com → Server: Identity
Product: Websites → Cloud Services
Comment 4•8 years ago
|
||
I'm not able to repro on latest Firefox release, so I wonder if it's something specific to your profile. :loz, can you please check whether you're able to login using a fresh Firefox profile?
Flags: needinfo?(liz)
Reporter | ||
Comment 5•8 years ago
|
||
Thanks. Yes, I can log in with a new profile. How can I figure out what in my regular profile is causing the problem?
Flags: needinfo?(liz)
Comment 6•8 years ago
|
||
My first guess would be a problem with localStorage or cookies. If you visit https://login.persona.org and open the debug javascript console, can you type in "localStorage" and successfully view the data that it's storing in your profile?
Reporter | ||
Comment 7•8 years ago
|
||
Hi Ryan. I'm not very familiar with using a debugger. I went to https://login.persona.org and then to Tools => Web Developer => Debugger. Was that the right thing to do? A section popped up at the bottom with a lot of HTML code (at least I think that's what it is). I put localStorage in the search box, but that didn't seem to change the code that was displayed. Am I doing something wrong? Thanks.
Comment 8•8 years ago
|
||
Sorry, I should have been more precise: * Visit https://login.persona.org * Open Tools => Web Developer => Web Console * Select the "Console" tab if it's not selected by default * Type "localStorage" into the prompt there and hit enter For me it looks like the attached screenshot.
Reporter | ||
Comment 9•8 years ago
|
||
Thanks. Here's what showed up: Storage { storageCheck: "true", returnTo: "null", usersComputer: "{"1163407":{"state":"confirmed","up…", emailToUserID: "{"ecompton@mozilla.com":1163407,"li…", main_site: "{}", siteInfo: "{}", stagedOnBehalfOf: "null", interaction_data: "{}", emails: "{}", managePage: "{}" }
Comment 10•8 years ago
|
||
Thanks, that looks like it was able to access the storage correctly. I'm unfortunately short on other things to suggest. Two more general things you could try: * Start in "Safe Mode" to see if it's bad interaction with some addon or similar [1] * Do a profile refresh to clear out any weird state that's in the profile [2] [1] https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode [2] https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings
Reporter | ||
Comment 11•8 years ago
|
||
In case this comes up with anyone else, the way I was able to fix the problem was to change, under Privacy Preferences, "Accept third-party cookies" from "Never" to "From Visited."
Comment 12•8 years ago
|
||
Thanks Liz, I will try to remember this if similar problems come up again in the future.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•