keepassium
Ability to enable Autofill *per Database*
Hi there,
It seems currently, it’s only possible to enable / disable / configure Autofill globally;
Please consider to implement the ability to do this, per Database.
I have multiple Databases, and i do not want some/all of these databases to unnecessarily expose themselves / “leak” data, to Spotlight or the underlying OS frameworks.
(if this is already possible somehow, please advise…)
Thank you!
You can already disable Quick AutoFill per database: https://support.keepassium.com/docs/database-settings/#quick-autofill
(As for standard AutoFill, the one with the full dialog, just avoid selecting databases that you don't want :)
Thank you for your reply. Yea i noticed that, and it's nice. However;
-
I'd rather not be bothered with yet another pointless choice / "selection" dialog.
-
I noticed i can configure to "automatically open the last database" - but i assume that would include the databases i do not ever want to use in Autofill.
It would be much more convenient (and safe) to be able to specify the database(s) we want to use with Autofill.
I'd rather not be bothered with yet another pointless choice / "selection" dialog.
A selection dialog is pointless only when there is only one option — in which case, KeePassium auto-selects it anyway.
If there is more than one database to choose from, the dialog is barely pointless.
I noticed i can configure to "automatically open the last database" - but i assume that would include the databases i do not ever want to use in Autofill.
Yes, it will be whatever database was opened last.
I have multiple Databases, and i do not want some/all of these databases to unnecessarily expose themselves / “leak” data, to Spotlight or the underlying OS frameworks.
This has nothing to do with AutoFill, though. If Spotlight tracks app behavior and opened files, this is more likely to apply to the main app.
It would be much more convenient (and safe) to be able to specify the database(s) we want to use with Autofill.
Perhaps I am missing some context here… Can you give an example of how selecting a wrong database in the list can realistically undermine one's (data) safety?
Just to be clear, the implementation is straightforward. I am reluctant because 1) it's an extra switch (one more step closer to feature bloat), but mainly because 2) there will be support emails like "help, my database has disappeared from AutoFill".
Thank you for the detailed explanation, much appreciated;
In my example below, let's stick to the most basic issue:
If there is more than one database to choose from, the dialog is barely pointless.
This is exactly my situation: i have multiple databases (currently 3.) Let's say database 1, 2 and 3. But i only ever want to use database 1 for Autofill (i never want the data of database 2 and 3 to be used/exposed to Autofill.)
So, showing a selection dialog for Autofill is pointless, and only causing more time/friction.
PS. Note that the Strongbox App (which i do not use) does exactly this, it allows users to specify Autofill settings per Database. Perhaps it can be useful to peek into how they've implemented the workflow.
Perhaps I am missing some context here… Can you give an example of how selecting a wrong database in the list can realistically undermine one's (data) safety?
No, i trust you when you say that's not the case. I don't know the exact mechanics / insight. The workst case i can imagine then, is me selecting the wrong Database (or the "automatically open the last database" setting, opening the wrong database for Autofill.)
This is exactly my situation: i have multiple databases (currently 3.) Let's say database 1, 2 and 3. But i only ever want to use database 1 for Autofill (i never want the data of database 2 and 3 to be used/exposed to Autofill.)
Well, having only one autofillable database is just one particular case. In a general case, one has N databases, of which M are used for AutoFill. So the ability to choose database is very relevant in general case.
Anyway, if you are concerned with accidentally selecting a wrong database and leaking one of its entries via AutoFill, there is an easy solution:
- Open that database in the app
- Tap the top-right menu → Edit Group
- Switch the "Password AutoFill" setting to "Disabled".
All the DB contents will be hidden from AutoFill. The file would still be listed — let's call this a design decision to reduce user confusion — but you won't be able to select any of its entries. (Ironically, the suggested setting does cause confusion too :)
Reopening to estimate demand, since the same request was made in #478.
Anyone who needs the ability to hide databases from AutoFill — leave a reaction in the top post so we can better prioritize this among other issues.