Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Support KP2A_URL_# attributes when accessing KyPass from other apps #21

Open
aaaskew opened this issue Sep 1, 2023 · 0 comments

Comments

@aaaskew
Copy link

aaaskew commented Sep 1, 2023

The problem
Web sites now have different FQDNs for their sign-in pages and their home pages now that they are are using OAuth2/OpenID Connect, etc for authenticaion. So you would want to put https://www.company.com/myaccount in the KeePass URL field but the username and password need to be filled in a web page served by https://signin.company.com/

What can be improved?
When other apps open KyPass to find the password for their URL, the list of entries presented should be filtered on URL field but also the KP2A_URL and KP2A_URL_1, KP2A_URL_2, ..., KP2A_URL_# fields. Using a filter like {URL}.* || {KP2A_URL}.* || {KP2A_URL_1}.* || ...

More information
These fields are used by other KeePass programs, like KeePassXC, to store sign-in URLs which might not be the same as the home page URL for better web browser integration. Among the KeePass managers supporting this feature are Keepass2Android, KeePassXC, KeeWeb, and possibly others.

For example for a Microsoft account:
URL: https://mail.live.com/
KP2A_URL: https://login.live.com/
KP2A_URL_1: https://login.microsoftonline.com/
KP2A_URL_2: https://account.microsoft.com/

This way the Microsoft account entry can be presented when signing in through any of these web pages.

See a similar request for KeePassium keepassium/KeePassium#180

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant