[Feature] Display tags for matching sites on the extension UI

[rocketraman]

Have you searched for an existing feature request?

• Yes, I tried searching

Brief Summary

I am proposing that the keepassxc browser extension show the tags I have configured for an entry on the extension UI, if the current page URL matches the entry.

My main use case: Oauth social logins e.g. Google, Facebook, X, GitHub, etc. are used more and more often.

For these types of logins, I store an entry in KeepassXC with a tag like oauth/google/personal to indicate an oauth login using my Google personal account. This tells me exactly how I should login to the web site. However, at the moment I have no idea what the mechanism is directly in the browser -- I have to look up the site in KeepassXC in order to see the tag and determine how to log in.

Secondary use case: I also associate tags with entries based on what information the site holds about me i.e. my address, my phone number, my email, credit cards and so forth. So having those tags displayed by the extension also gives me additional information about my privacy risks related to the site.

Given tags have many useful use cases, I'm sure there will be other use cases and benefits to this solution as well.

Related issue, but I am proposing an alternative solution to the problem: #735.

Example

No response

Context

No response

[varjolintu]

You can already show the group name where the entry is. Showing tags would make the Autocomplete Menu (and the entry list in the popup) even larger, and showing much more information than actually needed.

I suggest to use clear group names and titles if your goal is to find out different entries easily. We don't support additional entry types yes (address, credit card etc.) in KeePassXC yet. There's no point to add support for them to the extension yet.

[rocketraman]

Thanks for the reply. Unfortunately that doesn't work for me as I don't group entries by technical login type but rather by business criteria.

One suggestion could be to show the tags and possibly other details for an entry in a hover popup?

[varjolintu]

At least I can add the tags for the next protocol version that refactors most of the data that's transferred between the extension and KeePassXC. Those can be used later in the extension if needed.

[mcules]

+1 for exposing tags over the protocol — and I'd like to ask whether the write direction could be considered at the same time.

We're building an SSH client that resolves its connection credentials from KeePassXC over the browser protocol (so the master password never touches the app). Entry tags would be really useful for us in two ways:

1. Reading an entry's tags, to display and filter connections by tag (e.g. prod, staging, a customer name), and
2. Setting/editing tags from within the client and writing them back to KeePassXC.

Reading is already covered by your plan to add tags in the next protocol version, thanks for that! My question is about (2): could the refactored protocol also allow writing tags, e.g. an optional tags field on set-login (or a dedicated action), so a connected client can update an entry's tags? Today set-login only carries login/password/url, so there's no way to persist tag changes back to the database.

[varjolintu]

@mcules It could be possible, yes.