How to Disable Saved Address and Credit Cards
During a client Audit earlier this week we were dinged on not having the option in Firefox ESR to block manually saving Addresses and Credit Cards. We have the autofill disabled however users can still manually add credit cards and addresses and this poses an issue with our call center agents handling Credit Card info. I'd like to be able to gray out the Saved Addresses and Saved Credit Card boxes so as to prevent agents from manually entering card data into it using a GPO or Registry setting that we can push and apply to all our domain PCs. Ideally, if we could add an entry to the JSON preferences in the Mozilla GPO that would gray those options out that'd be best but any option that removes the users ability to add CC info would be acceptable.
Todas as respostas (9)
You can set the preferences
extensions.formautofill.creditCards.enabled extensions.formautofill.addresses.enabled
to false using the Preferences policy:
https://mozilla.github.io/policy-templates/#preferences
I'll get the official policies moved up on my todo list.
oh wait, you mean the buttons. Interesting. We don't have a way to disable those.
I'll get the policy implemented and it will disable those.
I'm looking at what chrome does and you can't add new addresses when you disable autofill.
I'm wondering if that's the right thing here? The button still works but you can't add new addresses?
Otherwise you wouldn't be able to remove addresses.
Thoughts?
Correct it's the buttons. I have those JSON lines in the preferences and that only removes the autofill checkboxes but the button can still be clicked and you can still add a credit card when autofill is disabled. See below what happens when I have the autofill checkboxes disabled but manually click on the saved credit card button. ***This is just a test CC number pulled from the web***.
Yeah, makes perfect sense. I'll get this done in the next week or so.
I'm curious if you've had any luck in finding a solution to this question.
Patch is being reviewed. It should be in Firefox 125/ESR 115.10
Just wanted to let you know that this did land in Firefox 125 and will be in the ESR 115.10.
Great news. Once that is released I'll give it a try and let you know if I have any other issues. Thank you for the update.