Disabling ability to save a sites login info and how to re-enable the feature to ALLOW it to be saved w/ keepass & kee mozilla plugin

[Tim Dickerson]

Hi

I just acidently told KeePass that I did NOT want to save this sites login information (using the kee plugin as well) and it must have stored that site in the 'don't remind me to bother asking the user' that queation type deal and I now would like to remove that site from the so called 'don't fill it in or bypass this site' list.

Does anyone know what file or option I can edit to change that?

Version: 3.4.3

Plug-in's: 1P2KeePass
Favicon Downloader
KeeAnywhere
KeePass RPC
VeraCrypt
Enhanced view
Serpent Cipher
Title Display
Kee - Firefox Extention 3.7.2

Tim Dickerson
ARS N9NU

Thank You

[T. Bug Reporter]

This page is old but maybe you can find the info you need there. The author of Kee (whom I shouldn't be speaking for because he reads this forum) seems to be concentrating on his own "Kee Vault" lately, and like most programmers, neglecting to update his documentation.

@luckyrat:
This is not meant as a dig; I do it too. Getting the program working always seems to eat into whatever time you set aside to write the docs.

[Horst]

For the Kee plugin this is controlled in the KeePass entry and not in Firefox.
Edit KeePass Entry, under the Kee tab there is "Hide this entry from Kee"

[Luckyrat]

The configuration options should be documented at https://forum.kee.pm/t/customise-appearance-and-behaviour-with-settings-options-preferences/2366

For this case, the section about the "Kee browser extension" is the relevant place to look. Telling Kee that you don't want to save a password for a specific site will record that information in the settings that are specific for that website so you can easily undo that action by changing the "Offer to save passwords" setting for that web page.

I think all the documentation on the support forum is up to date and I'm happy to refine it when necessary if feedback is provided. The page of old GitHub documentation is possibly getting old enough to be deleted entirely but I've intentionally left it there for a while as a courtesy to anyone that's been stuck using very old versions of Kee (KeeFox). Sorry that this has caused some confusion.

Thanks for the mention @t_bugreporter and trying to help out; I do check this forum but very regularly so it may have been some time before I spotted this. For future reference of others reading, issues relating to Kee (or Kee Vault) should typically be discussed on the forum I linked to above in order to get more relevant and faster information.

[Tim Dickerson]

Hi

Oh I wasn't intending it to be a bug report as I didn't think it even was. If that comment wasn't for me, then disregard. Lol

Tnx for the information on where to look and how to change that.

Tim
ARS N9NU

[Tim Dickerson]

I just re-read something. Is 'Kee' an older plugin where in 'KeeForm' is the newer one with the intent to replace it?

I should just be running ONE of them, correct? I don't mind (I just noticed) the $2 a month deal and would like to be using the latest version.

Is KeeForm a completely seperate standalone app to like replace KeePass 2.x.x or is it just an additional plug-in to do away with the auto-fill in deal with KeePass 2.x.x?

Tim

[Horst]

KEE browser plugins are replacements for KeeForm.
It uses KeePassRPC plugin to comunicate with KeePass database.

[Havokdan]

To my knowledge, the Kee extension is the successor of KeeFox extension, KeeForm's another plugin or extension.

[Horst]

Ops, you are right.
But KeeForm is very limited compared to Kee with KeePassRPC.
It only works if one starts an URL from KeePass.

[KeeForm]

Yes, this is intentional. I don't feel comfortable if a browser extension has a two-way communication channel with KeePass. That's why I keep maintaining KeeForm :-)