How can I use all open databases with Secret Service?

[AZMCode]

I have multiple databases, only one of which is storing SecretService credentials.
How can I make sure secretservice requests get routed to the right database, regardless of which one is selected in the UI?

[tt-a1i]

You do not need to keep that database selected. KeePassXC exposes each configured database as a separate Secret Service collection, and a service-level search checks every unlocked, exposed collection rather than just the active tab.

For this setup, I would expose only the database that holds the Secret Service entries:

1. Enable the integration under Tools → Settings → Secret Service Integration.
2. Open the credential database, then go to Database → Database Settings → Secret Service Integration and choose Expose entries under this group.
3. Leave Do not expose entries selected for the other databases.

There is one relevant detail: KeePassXC makes the default collection alias follow the active database when that database is exposed. Some clients use that alias when creating items. If only the credential database is exposed, switching to another normal database will not redirect those requests away from it.

[0xshubhs]

Nothing to do, routing doesn't follow the UI selection here.

A database only becomes a Secret Service collection if you enable Database Settings > Secret Service Integration > Expose entries under this group. Only one of yours has that, so it's the only collection on the bus and every request lands there.

One caveat: the default alias does follow the active tab. Service.cpp:81 wires activeDatabaseChanged to ensureDefaultAlias():

auto coll = findCollection(m_databases->currentDatabaseWidget());
if (coll) {
    coll->addAlias(DEFAULT_ALIAS).okOrDie();
}

The if (coll) is why you're fine. Switching to a non-exposed database returns null and the alias stays where it is.

It breaks the day you expose a group in a second database. If you get there, have clients use the collection's DBus path instead of default.