1181031 - Shared Cookie Jar

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[David Almström]

>> Feature Request Title:
Shared Cookie Jar

>> Description of feature, or problem to be solved
A shared cookie jar has been identified as needed in 3.0. There are at least two use cases:
1. user login simplified. I.e. today, if you are logged in to Facebook in one browser instance, a user still have to re-login to use Facebook Connect for authentication by another services.
2. there are no tracking methods for ads in FxOS today at all which makes the platform very hard to monetize for developers. On other mobile platforms, there are ad identifiers that ad networks can leverage.

>> Impact of implementing the feature/solution
For the use cases above:
1. Users will only required once to login and can save significant amount of time for accessing services, like they do today on the desktop
2. developers will have a better way to monetize for in-app ads, which is the largest revenue source for developers today.

>> Impact of NOT implementing the feature/solution
For developers, we are already seeing a decline of interest, continuously less support for ways to monetize will not make the decline less. 

>> Date required
in time for 2.5

Comment 1

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

The good news is that this is already in full progress. We're working on a new security model for FirefoxOS, which, among other things, gets rid of the separate cookie jars for separate apps. See [1] for a somewhat detailed description of what is getting implemented, and the dependency tree of bug 1149545 to see how work is progressing.

The bad news is that it's pretty aggressive to get all this done for 2.5. Our aim is to get it all done on that timeline, but it's a lot of code that needs to be written.

The other piece of bad news is that it'll require some changes on the marketplace website. App packages need to be converted to a new streamable packing format, rather than the current zip based format, and we need to host the packages on a separate domain name. The intent is that both these changes can be done in an automated fashion, without any need for manual input of either the marketplace team, or the authors.

However, again, this is a lot to get done in the 2.5 timeframe.

[1] https://wiki.mozilla.org/FirefoxOS/New_security_model

Comment 2

[David Almström]

thanks, much appreciated. I add the bug to keep in on the radar. But feel free to close it as I'm following the new security model metabug.

Comment 3

[BMO Automation]

Firefox OS is not being worked on