為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox requests a master password, even though the option is turned off.

  • 3 回覆
  • 1 有這個問題
  • 18 次檢視
  • 最近回覆由 Boyd_Roberts

more options

We have a website application that we access on a normal basis that requires credentials to access. Occasionally we encounter a user who is prompted to enter a master password, even though they do not have that option selected in Firefox, when they attempt to visit the site. Once the password prompt appears, Firefox no longer responds to any other commands and has to be killed from the Task Manager.

For most users, we can delete their profile and create a new one and that rectifies the problem (though we still cannot determine why it prompts them in the first place). Though there are some users who continue to be prompted even after a new profile is created. Is there a setting perhaps buried in the registry somewhere that may be forcing this prompt to occur?

We are using Firefox Version 24.5.0 (company wide forced usage, cannot upgrade)

We have a website application that we access on a normal basis that requires credentials to access. Occasionally we encounter a user who is prompted to enter a master password, even though they do not have that option selected in Firefox, when they attempt to visit the site. Once the password prompt appears, Firefox no longer responds to any other commands and has to be killed from the Task Manager. For most users, we can delete their profile and create a new one and that rectifies the problem (though we still cannot determine why it prompts them in the first place). Though there are some users who continue to be prompted even after a new profile is created. Is there a setting perhaps buried in the registry somewhere that may be forcing this prompt to occur? We are using Firefox Version 24.5.0 (company wide forced usage, cannot upgrade)

所有回覆 (3)

more options

Could that be anything to do with the web application itself ? Do such users ever see a similar problem attempting to use a webpage that requires login ?

I have not got Fx24 installed but IIRC the master password feature was similar to what it is now, and aborting a login does not lock up Firefox.

There are or were problems usually associated with Sea Monkey and Firefox. It does not surprise me that some of your users will have hit problems because I doubt they are using separate OS accounts or separate Firefox profiles.


One important consideration is users may have more than one Firefox Version Indeed they should have if for instance using laptops within your LAN and outside, otherwise an insecure Fx24 will be used outside on the Internet. Even if that is only a limited threat to your servers it is a severe threat to the laptops' Windows software.

It is absolutely vital to use separate Firefox profiles for each version. All versions do not even use the same files & systems probably part of the reason for your issues early versions used signons.txt , signons.sqlite was then used till fx31 then replaced in fx32 with logins.json

The easiest method of separating Firefox versions and ensuring that they have separate profiles may be to use separate OS accounts. Alternativley end users may use Firefox's custom install option, and Firefox's built in Profile Manager.

edit P.S. see also


No doubt you are aware that you are using unsupported versions of Firefox. General users are on Fx38 or above now. Enterprise users should be on Fx31.7 and preparing to switch to Fx38. See

由 John99 於 修改

more options

This is usually a problem with the key3.db file and can be fixed by deleting logins.json and key3.db. This will remove all saved passwords, so users need to make a note of saved passwords.


You can use this button to go to the currently used Firefox profile folder:

由 cor-el 於 修改

more options

Thank you both for your suggestions, I will attempt these solutions and see if they work.

We initially assumed it was an issue with the web application itself, but the vendor providing support for the app shunned it as a "browser issue".

Unfortunately, upgrading our FF is not an option as our PC software installations are determined by Group Policy settings, and cannot be overridden.