1641810 - Can’t login to Office 365 from certain Ubuntu/Windows machines

Status: NEW

(Core :: Networking, defect)

Description

[Anca Soncutean [:Anca], Desktop Release QA]

Attachment: Peek 2020-05-29 14-57.gif

Affected versions

• 77.0 - build 3
• 78.0a1

Affected platforms

• Ubuntu 18.04

Steps to reproduce:

• Try to log in into Office 365 with valid credential

Expected result

• The user is able to log in

Actual result

• The user can’t log in

Regression range

• Reproducible on old profile 67.0a1, but I’m certain this worked since then on my machine, so there are probably other interactions; note that on Chrome I have no problem to log in.

Additional notes

• Tested on 3 Ubuntu machines (2 - reproducible, 1 - not reproducible)

Comment 1

[Andrew Overholt [:overholt]]

I see a similar loop with my bank as of 2 days ago in Release on Linux. Don't know if it's related but maybe it is.

I feel like this might be a cookies-related issue and not a Widget-related issue but I'll let those more knowledgeable make that call.

Comment 2

[Tim Spurway [:tspurway]]

S1 or S2 bugs need an assignee - could you find someone for this bug?

Comment 3

[Andrea Marchesini [:baku]]

(In reply to Andrew Overholt [:overholt] from comment #1)

I see a similar loop with my bank as of 2 days ago in Release on Linux. Don't know if it's related but maybe it is.

I feel like this might be a cookies-related issue and not a Widget-related issue but I'll let those more knowledgeable make that call.

I'm not able to reproduce this issue with office.com. Can you please check if the issue is reproducible with pref network.cookie.sameSite.laxByDefault set to false? If yes, can you do the same test with pref network.cookie.sameSite.schemeful set to false?

Comment 4

[Anca Soncutean [:Anca], Desktop Release QA]

(In reply to Andrea Marchesini [:baku] from comment #3)

I'm not able to reproduce this issue with office.com. Can you please check if the issue is reproducible with pref network.cookie.sameSite.laxByDefault set to false? If yes, can you do the same test with pref network.cookie.sameSite.schemeful set to false?

No changes on my side, I can still reproduce the issue.

Comment 5

[Andrew Overholt [:overholt]]

(In reply to Andrea Marchesini [:baku] from comment #3)

(In reply to Andrew Overholt [:overholt] from comment #1)

I see a similar loop with my bank as of 2 days ago in Release on Linux. Don't know if it's related but maybe it is.

Can you please check if the issue is reproducible with pref network.cookie.sameSite.laxByDefault set to false? If yes, can you do the same test with pref network.cookie.sameSite.schemeful set to false?

Not sure if my bank problem is even the same issue but I can confirm laxByDefault is set to false and the schemeful pref doesn't exist in release on Linux where I'm having the issue. (FWIW I can log in in a new profile)

Comment 6

[Jim Mathies [:jimm]]

Definitely not a widget bug. Pushing up to Firefox, maybe they can find an owner. A regression range would be helpful.

Comment 7

[Mike Kaply [:mkaply]]

I think we need some more info here.

So it's definitely Linux only? Not on any other systems?

Can you check the Javascript log for errors?

Which specific office365 URL are you using?

Comment 8

[Anca Soncutean [:Anca], Desktop Release QA]

(In reply to Mike Kaply [:mkaply] from comment #7)

So it's definitely Linux only? Not on any other systems?

• I can only reproduce it on Ubuntu; I’ve double checked with two of my colleagues with Ubuntu 18 (when the issue was submitted), one reproduced the issue, one didn’t. Windows, Mac are not affected.

Can you check the Javascript log for errors?

• https://drive.google.com/file/d/1bfaC5IzMBhNCSnfe12bNQrzvHHJEqoOU/view?usp=sharing

Which specific office365 URL are you using?

• link 1 or link 2 .. none of them work on Firefox, while on Chrome I have no problem to log in.

Comment 9

[Mike Kaply [:mkaply]]

I did a quick check for me and I can login on Ubuntu. I'm at a loss on what to do with this one.

Comment 10

[Catalin Sasca, QA [:csasca]]

Happened to me on Windows 8.1 on two clean profiles on beta 80.0b6.

Comment 11

[Dragana Damjanovic [:dragana]]

Is his still reproducible?
Can you make a http log:
https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Comment 12

[Daniel Cicas [:dcicas], Release QA]

Hello,

I can still reproduce this issue in 82.0b7 I will attach the log file. Here is a the HTTP LOG

Comment 13

[Kershaw Chang [:kershaw]]

I took a quick look at the log, but can't find anything fishy.

The js error message in comment #8 regarding to LoginManagerChild.jsm seems suspicious.
https://drive.google.com/file/d/1bfaC5IzMBhNCSnfe12bNQrzvHHJEqoOU/view?usp=sharing

:Mardak, could you take a look at the js error message? Does this error message have something to do with this bug?

Comment 14

[Gabi Cheta [:Gabi] Release Desktop QA]

Issue is reproducible with Windows 7x64, Firefox 83.0 and Firefox Nightly 84.0a1. On Google Chrome Office 365 works fine.

Comment 15

[Bodea Daniel [:danibodea]]

I can't reproduce it on my Ubuntu 20/Windows 10. Do we suspect any specific causes for this issue?
Does it still reproduce on the bug's original OS/system?

If it is not an intermittent issue, then maybe a regression investigation with mozregression could be performed.
What do you think, Anca?

Comment 16

[Anca Soncutean [:Anca], Desktop Release QA]

(In reply to Bodea Daniel [:danibodea] from comment #15)

I can't reproduce it on my Ubuntu 20/Windows 10. Do we suspect any specific causes for this issue?
Does it still reproduce on the bug's original OS/system?

If it is not an intermittent issue, then maybe a regression investigation with mozregression could be performed.
What do you think, Anca?

This issue is still reproducible on my Ubuntu 18.04 with the latest Nightly/Beta versions. On the affected test machines, the issue is 100% reproducible. Any regression investigation is redundant, something seems to trigger this issue at the OS level, I’ve double checked with an older Firefox (version 54) and the login problem manifests there too, but as mentioned in bug’s descriptions, I know for a fact, on versions close to the one on which the issue was first encountered, at some point the login functionality worked (note that a simple Office 365 login is a test frequently run by our team). Apart from what was already mentioned as additional information by me and my colleagues, not sure what interaction could be the main cause here (note that logging works just fine on Chrome, using the same test machine). At this point we can only provide any other more specific info if requested.