Open Bug 1319761 Opened 8 years ago Updated 7 months ago

Login on pinterest using facebook social network not working on Fx with FPI

Categories

(Core :: DOM: Security, defect, P3)

defect

Tracking

()

Tracking Status
platform-rel --- -
firefox50 --- unaffected
firefox51 --- unaffected
firefox52 --- unaffected
firefox53 --- affected
firefox64 --- affected
firefox65 --- affected
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected

People

(Reporter: bmaris, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tor] [domsecurity-backlog1][platform-rel-Facebook])

Attachments

(1 file)

[Note]:
- Prerequisits:
Enable perf "privacy.firstparty.isolate"
Disable perf "network.predictor.enabled"
Disable perf "network.predictor.enable-prefetch"

[Affected versions]:
- latest Nightly 53.0a1

[Affected platforms]:
- Ubuntu 16.04 32bit

[Steps to reproduce]:
1. Visit pinterest.com
2. Click Continue with Facebook
3. Enter user and password for Facebook and click Log-in

[Expected result]:
- Fx successfully completes the log-in process using Facebook.

[Actual result]:
- After login a blank page is displayed in the new opened pop-up and the log-in using Facebook social network is a success.

[Regression range]:
- This is not a regression, It's still an experimental feature not enabled by default in any official build.

[Additional notes]:
- Screenshot attached showing the error.
Has Regression Range: --- → no
Has STR: --- → yes
QA Whiteboard: [qe-fpi]
[Additional notes]:
- I should have mentioned that I did not encounter the same issue on Tor Browser.
This bug can be reproduced on Mac OS as well.
Priority: -- → P1
Whiteboard: [tor] → [tor] [domsecurity-backlog1]
Assignee: nobody → tihuang
platform-rel: --- → ?
Whiteboard: [tor] [domsecurity-backlog1] → [tor] [domsecurity-backlog1][platform-rel-Pinterest]
Whiteboard: [tor] [domsecurity-backlog1][platform-rel-Pinterest] → [tor] [domsecurity-backlog1][platform-rel-Facebook]
platform-rel: ? → -
It looks like that there will be no more a blank 'facebook.com' page after turn off pref "privacy.firstparty.isolate.restrict_opener_access". The log-in process, however, is still not complete that Pinterest does not log-in successfully. It implies there are still some issues here. I will try to figure out.
This is an assigned P1 bug without activity in two weeks. 

If you intend to continue working on this bug for the current release/iteration/sprint, remove the 'stale-bug' keyword.

Otherwise we'll reset the priority of the bug back to '--' on Monday, August 28th.
Keywords: stale-bug
Keywords: stale-bug
Priority: P1 → P2
Assignee: artines1 → nobody
Priority: P2 → P3
FWIW the cause of the problem here is that after the popup where the login happens is closed, an iframe on the main page is navigated to a place like https://www.facebook.com/connect/ping?client_id=xxx&domain=www.pinterest.ca&origin=1&redirect_uri=https://staticxx.facebook.com/connect/foo/bar.js?version=42.  Without FPI, this iframe is loaded with facebook's cookies which were set by the pop-up.  With FPI, the popup is loaded under the facebook first party context so those cookies aren't present when navigating to this URL in the iframe and this breaks the login flow.

Updating flags

OS: Linux → All
Version: 53 Branch → Trunk
Severity: normal → S3

Flagging this bug as it has been accumulated a lot of spam. Can we restrict comments?

Restrict Comments: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: