Closed Bug 1475124 Opened 6 years ago Closed 6 years ago

identity.launchWebAuthFlow doesn’t work when privacy.firstparty.isolate is enabled

Categories

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

Product:
Core
Component:
DOM: Security
Version:
61 Branch
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: code, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-backlog2]) 

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180625102006

Steps to reproduce:

1. Set privacy.firstparty.isolate to true.
2. Use browser.identity.launchWebAuthFlow() in an extension.


Actual results:

Extension promise is never fulfilled.


Expected results:

Extension should have receive a promise from browser.identity.launchWebAuthFlow() containing the redirected URL following the auth process.
Based on the blocking meta bug I am putting under core:dome-security.

Daniel, 
If this needs triaging, please provide more information. 

I installed  First Party Isolation extension -> debug and run "browser.identity.launchWebAuthFlow()", the result is "TypeError: browser.identity is undefined"

If I missed steps, please provide all the steps.  Thanks
Component: Untriaged → DOM: Security
Flags: needinfo?(code)
Product: Firefox → Core
Priority: -- → P3
Whiteboard: [domsecurity-backlog2]
Marking this bug as wontfix as we need more information. Please reopen with more information.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.