Open Bug 1376767 Opened 7 years ago Updated 2 years ago

[FirstPartyIsolation] Social login on not working with FPI


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




Tracking Status
fennec + ---
firefox55 --- affected
firefox56 --- affected


(Reporter: ohorvath, Unassigned)


(Blocks 1 open bug)


(Whiteboard: [domsecurity-backlog1])

Create the perf ""privacy.firstparty.isolate"" and enable it 
Disable the perf ""network.predictor.enabled""
Disable the perf ""network.predictor.enable-prefetch"" 
Disable the perf ""browser.safebrowsing.malware.enabled""
Disable the perf ""browser.safebrowsing.phishing.enabled"" 
Create the perf ""privacy.firstparty.isolate.restrict_opener_access"" and Enable it

Steps to reproduce:
1. Go to and open the login page.
2. Tap one of the social networks to login with.

Expected results:
The social network login page is opened and users can login with that account.

Actual results:
Social login doesn't work. The login button is still displayed and there is no sign that the user is logged in.
tracking-fennec: --- → ?
QA Contact: oana.horvath
Ethan, would you help check if this is something TPE SecEng team going to take? Thanks.
Flags: needinfo?(ettseng)
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
A similar problem with another website. Tim, please look into this as well.
Assignee: nobody → tihuang
Flags: needinfo?(ettseng)
[triage@0719] +, as SecEng team is taking it.
tracking-fennec: ? → +
Assignee: tihuang → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.