Windows SSO Login does not work with Multi-Account Containers

[anupammajhi]

Before submitting a bug report

• I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
• I searched for existing reports to see if it hasn't already been reported

Step to reproduce

1. Open a new Multi-Account Container
2. Attempt to Login to website that uses Windows SSO (In my case AWS Management Console with Windows SSO)
3. Does not present SSO option, instead asks for credentials.

Note:

1. Using same steps I get SSO option in a normal "non"-Container tab
2. Option is already enabled in Firefox Settings (Allow Windows single sign-on)

Actual behavior

Does not present Windows SSO screen.
Redirects to page where I can provide credentials instead.

Expected behavior

1. It should present the Windows SSO screen with accounts that have been configured in OS Settings.
2. Even though a container is isolated from other sessions/containers, we should be able to choose whether to allow Windows SSO on those containers or not. Instead, the Firefox Settings page in container show the same option as it would in a default tab.

Additional informations

No response

Provide a copy of Troubleshooting Information page (optional)

No response

[scubasunny]

I really vote to get this bug fixed.
I'm using the Multi-Account Container very heavily and in addtion in multiple SSO environements.
Whereas it works with Keycloak, it doesn't work with the Microsoft SSO login via the connected Windows Desktop

[egallyg]

I might be wrong, but is this related?
https://github.com/mozilla/multi-account-containers/wiki/Frequently-asked-questions#enable-windows-sso-in-a-specific-container
I used the Boolean Key + Container ID successfully for my own PC - i.e. my company's 365 tenant works with SSO correctly in its designated container

Also posisbly related...
https://bugzilla.mozilla.org/show_bug.cgi?id=1836016

#2393