4 ms·

It would be nice to allow users to create "trusted tuples" to list small groups of domains that are allowed to share their cookies. For instance: Zendesk, Asana

It would be nice to allow users to create "trusted tuples" to list small groups of domains that are allowed to share their cookies. For instance: Zendesk, Asana, Jira, etc. But have each tuple listed still be isolated from the other, only domains listed together in a single list could share a cookie container.

InCityDreams 4y ago
...as opposed to 'nested tuplets'? /fz
laerus 4y ago
Probably that is the use-case for the official multi-account containers plugin.
- TheNewsIsHere 4y ago
  I tend to agree, but as someone who uses this plugin a LOT, I have some complaints. If I decide I want, say, an Azure Portal container then I cannot have login.microsoftonline.com assigned to a different container -and- configured to automatically open in that container. If I do that, I need to have a combined Azure + Office 365 + anything-I-need-to-authenticate-to-Azure-AD-for container. It’s a good solution but with its lack of flexibility I find it’s too far in the direction of security versus convenience.
  - bitwrangler 4y ago
    I use multi-account containers too, and I like it. This is exactly my point, instead of mapping each domain into a single container, any domain could exist in one or more "trusted tuples" Maybe another way to think of it is like a one-to-many join. A domain would not "belong" to a single container, but have tags to associate with 1+ containers.
zagrebian 4y ago
> small groups of domains that are allowed to share their cookies Could you explain how this could be beneficial to the user?
- 89vision 4y ago
  for non-dark pattern use cases where it is beneficial from a usability standpoint to share cookies across domains
  - zagrebian 4y ago
    Well, what are those use-cases? That is what I asked.
    - Rastonbury 4y ago
      SSO across multi-domain, Github logins, using Youtube.com and Gmail.com with the same G account. Assuming this is done the same way as existing Multi-containers feature
  - bitwrangler 4y ago
    Yes, I think there are some cases where a user might want to opt-in and allow cookies to be shared across a specific set of domains. The main reason I could think of it to allow cross-site business integration to continue to work as (currently) designed.
emsixteen 4y ago
Little bit of an aside, but what's the use-case for Asana here?

InCityDreams 4y ago

...as opposed to 'nested tuplets'? /fz

laerus 4y ago

Probably that is the use-case for the official multi-account containers plugin.

TheNewsIsHere 4y ago
I tend to agree, but as someone who uses this plugin a LOT, I have some complaints. If I decide I want, say, an Azure Portal container then I cannot have login.microsoftonline.com assigned to a different container -and- configured to automatically open in that container. If I do that, I need to have a combined Azure + Office 365 + anything-I-need-to-authenticate-to-Azure-AD-for container. It’s a good solution but with its lack of flexibility I find it’s too far in the direction of security versus convenience.
- bitwrangler 4y ago
  I use multi-account containers too, and I like it. This is exactly my point, instead of mapping each domain into a single container, any domain could exist in one or more "trusted tuples" Maybe another way to think of it is like a one-to-many join. A domain would not "belong" to a single container, but have tags to associate with 1+ containers.

zagrebian 4y ago

> small groups of domains that are allowed to share their cookies Could you explain how this could be beneficial to the user?

89vision 4y ago
for non-dark pattern use cases where it is beneficial from a usability standpoint to share cookies across domains
- zagrebian 4y ago
  Well, what are those use-cases? That is what I asked.
  - Rastonbury 4y ago
    SSO across multi-domain, Github logins, using Youtube.com and Gmail.com with the same G account. Assuming this is done the same way as existing Multi-containers feature
- bitwrangler 4y ago
  Yes, I think there are some cases where a user might want to opt-in and allow cookies to be shared across a specific set of domains. The main reason I could think of it to allow cross-site business integration to continue to work as (currently) designed.

emsixteen 4y ago

Little bit of an aside, but what's the use-case for Asana here?