Open vit9696 opened 3 years ago
Actually this can be moved one step further by integrating https://github.com/apple/password-manager-resources. This package has a large number of domain names, and it also includes shared names. By gluing this database with the user database we can get alias URLs even without manually specifying KP2A_URL_#
fields.
I wonder if this feature is on the roadmap? Without a paid developer license, I even cannot implement it on my own and create a pull request.
@zeyugao , the issue is open, so the feature is on the roadmap. Not a priority at the moment, though…
In KeePassXC I have KP2A_URL as well as KP2AURL# entries. This would indicate the need to support both the field without the _# and that including a number.
What can be improved? Several websites may have different URLs for login with sometimes these URLs having completely independent domains. Let's say
okko.tv
andokko.sport
. In many password managers it is natural to add multiple URLs to a login to allow autocompletion on both domains.The solution you'd like A commonly adopted solution is to use
KP2A_URL_#
fields for additional URLs. Here#
stands for a number starting with 1. This is what I got after importing my 1Password database into KeepassXC. Among the KeePass managers supporting this feature are Keepass2Android, KeePassXC, KeeWeb, and possibly others.The solution would consist of two parts:
URL
,KP2A_URL_1
,KP2A_URL_2
, and so on are matched first.KP2A_URL_#
fields likeURL (#)
.Alternatives you've considered Reinventing the wheel does not feel right here, despite
KP2A_URL_#
not being well-documented anywhere.Additional context The issue was partly mentioned in https://github.com/keepassium/KeePassium/issues/163, but may only be relevant to the display part.