We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

GUI Bug When Applying GPO

  • 1 Mbohovái
  • 0 oguereko ko apañuãi
  • 17 Hecha
  • Mbohovái ipaháva Dom Langella

more options

Hello,

Applying Preferences & Extension Management GPO's will bug certain GUI settings. The three examples I have are HTTPS-Only Mode & Forms and Autofill within about:preferences, and Enable USB Devices within about:debugging.

When HTTPS-Only Mode is set to "Don't Enable HTTPS-Only Mode" and locked via Preferences GPO, Users can continue to toggle between the settings. Forms and Autofill settings will not populate within about:preferences if address and credit card formfill values are false and locked via Preferences GPO. However, when the same GPO is deployed from Active Directory, Forms and Autofill settings will populate with address available for User toggle. Key, the values within about:config reflect what is set via GPO, and do not change among toggle or User intervention.

When locking down Enable USB Devices within about:debugging by blocking the extension install via Extension Management GPO, Users can continue to toggle the button after the policy applied. Although, just as previously mentioned, the extension does not get installed and seems the policy intervenes.

My questions being, are these simply GUI bugs since the values respect group policy? Are there other methods to lock down these settings?

I understand this is quite a bit of information and appreciate your help and time!

Preferences JSON - { "extensions.formautofill.creditCards.available": {

   "Value": false,
   "Status": "locked"
 },

"extensions.formautofill.creditCards.enabled": {

   "Value": false,
   "Status": "locked"
 },
 "browser.formfill.enable": {
   "Value": false,
   "Status": "locked"
 },
 "extensions.formautofill.addresses.enabled": {
    "Value": false,
    "Status": "locked"
 }

}

Extension Management JSON - { "adb@mozilla.org": { "installation_mode": "blocked" } }

- Dom

Hello, Applying Preferences & Extension Management GPO's will bug certain GUI settings. The three examples I have are HTTPS-Only Mode & Forms and Autofill within about:preferences, and Enable USB Devices within about:debugging. When HTTPS-Only Mode is set to "Don't Enable HTTPS-Only Mode" and locked via Preferences GPO, Users can continue to toggle between the settings. Forms and Autofill settings will not populate within about:preferences if address and credit card formfill values are false and locked via Preferences GPO. However, when the same GPO is deployed from Active Directory, Forms and Autofill settings will populate with address available for User toggle. Key, the values within about:config reflect what is set via GPO, and do not change among toggle or User intervention. When locking down Enable USB Devices within about:debugging by blocking the extension install via Extension Management GPO, Users can continue to toggle the button after the policy applied. Although, just as previously mentioned, the extension does not get installed and seems the policy intervenes. My questions being, are these simply GUI bugs since the values respect group policy? Are there other methods to lock down these settings? I understand this is quite a bit of information and appreciate your help and time! Preferences JSON - { "extensions.formautofill.creditCards.available": { "Value": false, "Status": "locked" }, "extensions.formautofill.creditCards.enabled": { "Value": false, "Status": "locked" }, "browser.formfill.enable": { "Value": false, "Status": "locked" }, "extensions.formautofill.addresses.enabled": { "Value": false, "Status": "locked" } } Extension Management JSON - { "adb@mozilla.org": { "installation_mode": "blocked" } } - Dom

Opaite Mbohovái (1)

more options

Any updates on this?

Thanks, Dom