Using containers for multiable identitys on websites

[lnee94]

How this would work.

• add option to select a set of containers to open a site in.
• when you go to example.com it should first open a landing page with an option set of which container to open in. (it should to have the option to use a list style or a grid style)
• Integration with password manager to set default login for a container. One way of doing this say add a data store where extensions can store anything in there (there would need to be a public for all extension and maby a private one too). and add a API that would allow extensions to set if a login shows as default. (NOTE this does not need to implemented for the other features to be useful it's just a nice to have)
• the ability to set the container icon to a data URI or a favicon.

What is the use case.
The main one I can think of is you have two accounts for one website loging out and loging in would suck and have to go to the extension is jank and out of the way so have a nice soft landing page for this perpus would make the usage experience for account hopping better then chrome.

[lnee94]

With this you could use the proxy containers extension to have the option to visit in tor or i2p or public

[lnee94]

Something that is also on the table is an option to not save history and an option to not save cookies (each option would not be linked, e.g. truth table would be 00 01 10 11) for a container

[kelimuttu]

Interesting! I can see how this can be useful for a heavy user of the multi-account-container feature. Maybe document this as a feature request?

[achernyakevich-sc]

@kelimuttu

It would be possible to achieve this if we will have implemented that we discuss in #2687 - user will need to add URL to some "default" container but do not confirm by ticking checkbox Remember my decision for this site. So every time he will be asked and will be able easily select container that should be used this particular time.

I think we could link discussions and move to that one.

[kelimuttu]

It seems that this one is more about bulk-action, though. I can imagine this is more useful for heavy-users with multiple accounts on a platform.

[NiklasBr]

more useful for heavy-users with multiple accounts on a platform.

It would help me, I have two accounts on BitBucket for two separate organisations:

• One accesses bitbucket.org/foo
• The other bitbucket.org/bar

Because the shared domain I cannot click the Remember my decision checkbox which is also very annoying because of how many tabs I need to open and close to work effectively. I ended up moving one org to another browser.

[kelimuttu]

@NiklasBr Makes total sense! Would you or @lnee94 open a new issue to document this as a feature request? Thanks!

[influential-eliot]

Not meaning to sound negative, as I think I'm very much for this idea ... but ... ... I think I already use MAC in this fashion with MAC + KeePassXC ... what am I missing that this provides already?

( given that it's not a good idea to keep passwords in any browser ... )

[achernyakevich-sc]

This is more about opening necessary container depending on the URL of services that support tenants/orgs and expose it in URL. For example GitHub:

• https://github.com/companyA/ - reference to GitHub organisation companyA that I need be logged in as UserA and would like to automatically open it in the container GitHubA.
• https://github.com/companyB/ - reference to GitHub organisation companyB that I need be logged in as UserB and would like to automatically open it in the container GitHubB.

AWS has similar but in the server name.

[aaribaud]

There is also the case of different containers, e.g. one for the admin user and one for a non-admin user, for exactly the same URL.

[influential-eliot]

Ah, OK, I have made my own way of dealing with this ... I utilise the redirector extension and effectively just make bookmarks for fake .local domains ... then I parameterise my subdomains with what I need to do to access a given thing.

I imagine that a cleaner version of this could be done utilising the @moz-document stuff ... making that relevant, again. :)

@moz-document [ <url>                    |
            url-prefix(<string>)     |
            domain(<string>)         |
            media-document(<string>) |
            regexp(<string>)
          ]# {
  <group-rule-body>
}

[s3r3n3ty]

TLDR: underlying functionality already exists, but UI is sub optimal + idea for a better UI flow

I switched to Firexfox just for this extension, expecting pretty much what op is after as well, being able to seamlessly switch between multiple accounts for a given site.

Now functionally this is absolutely possible, but the UI for this use case is terrible.

create container1 > open site in container1 > log into account1 > set to site to always open in container1 > create container2 > open site in container2 > log in to account2 > use 'repoen site in' to switch accounts > lots of site / account specific containers will now clutter the container menus.

Instead create a new option 'log in with other account'.
This will create a container that's only meant for a specific site and account and will not show as a general container, to reduce clutter in the container menus. (I currently have 15 account & site specific containers and it's getting rather cozy)
Or in other words, if a container is created through the 'log in with other account' option, that container will only show up as an option for that site (with an option to add other domains that use the same account)

open site > log into account1 > press 'log in with other account' in extension menu > log in with account2 > switch accounts (under the hood containers) by

1. clicking on the account name listed at the top of the extension menu with the account first logged into opening as default (opening the site in the container that was first used to log into the site) *
   OR as op already suggested
2. a landing page, with keyboard navigation (number keys instantly open respective accounts or arrow keys and enter)

account names are extracted when user logs in and set as container name by default, but are editabel by the user, in case the log in is an email or phone number instead of the actual user name)

As a bonus, at least for popular sites, profile pictures could be extracted with a formula, to be displayed next to the username for a quicker visual cue to the user.

Really hope this gets traction, since the underlying functionality is there. It's just the UI that needs to be improved.
If there's actual interest in this and I'm not just screaming into the void, I'd be glad to build a UI prototype to help make this a reality, since code is not my specialty.

*since simply logging into a site will not create an account specific container, clicking on the first account would open the general container that was used to first log into the site, but if for a given site there have been no log ins on any container yet, the option 'log in with other account' shows up as 'create container for login' (or something along those lines), while leaving the option functionally identical.