Access Connector icon dissappears randomly and active status changes to inactive when restarting
Categories
(Enterprise Products :: Firefox, defect)
Tracking
(Not tracked)
People
(Reporter: mcurtean, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Found in
enterprise-main build 152.0a1 20260424081038
Affected versions
enterprise-main build 152.0a1 20260424081038
Affected environment
Stage
Tested platforms
MacOS Tahoe 26.3
Preconditions
Admin access to Stage console .
Access Connector policy Applied in console
{
"Host": "proxy.enterfox.eu",
"MatchPatterns": [
"https://*.mozilla.org",
"https://mozilla.org",
"http://enterprise-console-static.default.svc.cluster.local",
"http://rustfs.rustfs-svc.svc.cluster.local"
],
"Port": 443
}
Firefox is installed.
Steps to reproduce
- Log in on FxE using SSO and acess about:policies.
- Check that the policy is correctly applied.
- Check that the AccessConnector icon is available in the toolbar on both active (domains that match the policy) and inactive domains (all other domains)
- Perform more actions: open a new tab, enable/disable a live policy such as DisableDeveloperTools and perform a restart.
Expected result
AccesConnector icon is available in the toolbar once the policy is active and it is generally inactive and active only on the domains matching the policy.
Actual result
AccessConnector policy is active in about:policies, and is active on the selected domains after first run - see Access Connector broken on first run.
Policy icons disappears randomly (I have not been able to pinpoint the exact steps), but it occurred shortly after restart - see video.
Policy switches from active to inactive as well after restart or seemingly after making changes to another live policy .
|
||
Comment 1•2 months ago
|
||
This may be what we are working on in https://bugzilla.mozilla.org/show_bug.cgi?id=2034591 ?
|
Reporter | |
Comment 2•2 months ago
|
||
This issue is no longer reproducible and was caused by server-side changes at the time of testing, so I am setting it as Invalid.
|
||
Comment 3•2 months ago
|
||
@alissy was debugging Access Connector earlier and was toggling the policy globally in staging console (he did not know you can set this per user), perhaps you were testing during the time he was also testing?
Let us know if you can reproduce this one again, otherwise I think that may have been what was happening
|
|
Reporter | |
Comment 4•2 months ago
|
||
(In reply to Josh Porter from comment #3)
@alissy was debugging Access Connector earlier and was toggling the policy globally in staging console (he did not know you can set this per user), perhaps you were testing during the time he was also testing?
Let us know if you can reproduce this one again, otherwise I think that may have been what was happening
Yes, thank for letting me know. He informed me and I re-tested after and the feature was stable, see comment 2
Description
•