Closed Bug 751310 Opened 8 years ago Closed 8 years ago
ensure Yahoo identity provider works in runtime
Yahoo accounts need to be whitelisted in the desktop runtime, as apps can integrate with yahoo.com addresses. An example of this application is LucidChart (https://marketplace.mozilla.org/en-US/app/lucidchart/?src=ss), which upon logging in, allows the user to login with their yahoo.com address through integrating with yahoo's account management service. The fix to this would be to add the origins yahoo's account management service uses to our whitelist for origins. Note: This does not block app functionality from the 30 or so apps I looked at for the signoff for marketplace beta, it just removes the ability in LucidChart to use yahoo.com accounts. Definitely important going forward though.
Marking as marketplace-beta=, as this does not block primary app functionality, but it would really good to have to ensure that yahoo account management works.
For k9o this is primary account integration use case for web apps, so nominating the bug k9o.
blocking-kilimanjaro: --- → ?
Priority: -- → P1
Whiteboard: [marketplace-beta=] → [marketplace-beta=] [blocking-webrtdesktop1+]
Target Milestone: --- → M1
Whiteboard: [marketplace-beta=] [blocking-webrtdesktop1+] → [blocking-webrtdesktop1+]
Component: Desktop Runtime → Webapp Runtime
Product: Web Apps → Firefox
Our strategy for fixing this is to fix bug 752666, so marking the dependency accordingly, and taking this bug (because I took that one).
Assignee: nobody → myk
Status: NEW → ASSIGNED
Depends on: 752666
Summary: Yahoo account management site needs to be whitelisted for the desktop runtime - Cannot use yahoo accounts in runtime → ensure Yahoo identity provider works in runtime
Moving to resolved fixed - dependency should fix this.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [blocking-webrtdesktop1+] → [blocking-webrtdesktop1+], [qa+]
Status: RESOLVED → VERIFIED
Whiteboard: [blocking-webrtdesktop1+], [qa+] → [blocking-webrtdesktop1+], [qa!]
You need to log in before you can comment on or make changes to this bug.