This project has moved and is read-only. For the latest updates, please go here.

browser integration url search logic

Oct 5, 2016 at 12:45 AM
I'm not sure I understand the search logic that's being used when I select the Share->K2A Find Password menu option. For instance: I have several logins with chase bank, all titled "chase" in my kdb. When I go to chase using android chrome, the login url is If I then select Share->K2A Find Password, it automatically chooses one of my chase entries, rather than showing me a list of all of them to choose from. It seems to be the one entry that has in its "URL" field (the others have blank URL fields).

The official keepass client uses the entries' Title fields for searching. Does K2A not do the same?
Nov 7, 2016 at 10:06 AM
KP2A does not consider the Title, but only the URL field.
Jun 12, 2017 at 3:15 PM
Is there any published info/doc on exactly how the browser URL matches with the KP URL field? Can we use wildcards in the KP entry URL field?

This is the only area where my usage of KP2A stutters. As others have said, we need to open the app, manually select an entry, and come back to the original app. I usually use Android Firefox. KP2A usually offers an entry based on the browser app's ID, which is meaningless in this context. Sorry if I've missed something obvious.

Thanks for this app!!!!!!!!!!!!!!! I switched to using this from one of the other Android apps and have not gone back.