ContextualIdentity API: Add ability to assign sites to a container
Categories
(Core :: Security, enhancement)
Tracking
()
People
(Reporter: sdk, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [design-decision-needed])
Why
Some extensions using the ContextualIdentity API offer a way to assign sites (domains, URL patterns) to a container. Implementing this feature on the addon side has some limitations. An example is that assignments from addons can conflict with each others and open the doors to data leaks or tab loading ending in an infinite loop.
| Reporter | ||
Updated•3 years ago
|
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Toolkit::Add-ons Manager' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
We would very much support this addition to the API, but the underlying platform code would need to support the feature first. Not sure if there is a more specific component, so moving to Firefox::Security for now.
Comment 3•3 years ago
|
||
Oh looks like the ContextualIdentity meta bug is in Core::Security.
Note that there are a number of requests on every site assignment add-on currently (e.g. mozilla/multi-account-containers#1749, kintesh/containerise#171) to allow for a website to be assigned to several containers.
The use case is to stay logged in with several accounts on the same domain, say e.g. you have a microsoft/outlook account from your employer, and one for your personal email.
If Firefox internalizes the assignment API, it’d be nice to make it possible for containers to be used that way from the start.
Updated•3 months ago
|
Description
•