Open paulmartinidea opened 1 year ago
We are experimenting the same issue. Container tabs no longer send the Device info/state (Device Type, Compliancy state, etc). Without this info, we cannot login as AAD conditionnal access requires us to be working from Hybrid joined device.
We also have the same issue.
Could the issue be firefox itself along with Containers? I would suggest filing a report on BugZilla as well because the issue may be Firefox itself.
Logging on Firefox without containers works on version 113 just not when using the container
I've reported this defect in Bugzilla
Hi all,
The bugzilla defect was closed, as it is an intented behavior from this defect. There's a solution however (from the later defect):
containers.json
in your Firefox profile directory, in a key called userContextId
(47001
for example)about:config
, create a boolean key network.http.windows-sso.container-enabled.CONTAINERID
, where CONTAINERID
is from step 1. Set this key to true
It would be great to put in the [FAQ], but I don't have the edit rights. In the meantime, this bug can be closed
@Chouffy Great work!
It would be great to put in the [FAQ], but I don't have the edit rights.
@dannycolin Could you help to enhance documentation?
Done. I'll keep this bug open for now so we can redirect any duplicate to this one.
Before submitting a bug report
Step to reproduce
Open new containers attempt to login to site ( in this case AWS Managment Console which is using SSO and Endpoint protection) A bad request 400 is received once the login process completes
Actual behavior
An error message is presented when attempting to login
Expected behavior
Login is successful.
Additional informations
This only started happening since upgrading Firefox to version v113, downgrading to v112 allows this to work as expected.
The main difference we can see from our sign in logs is that in version 113 the "Device ID" and "Join Type" is not present on the Azure side.
Provide a copy of Troubleshooting Information page (optional)
No response