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

Support multiple URLS #109

Closed
1 of 3 tasks
lsouchet opened this issue Feb 22, 2018 · 3 comments
Closed
1 of 3 tasks

Support multiple URLS #109

lsouchet opened this issue Feb 22, 2018 · 3 comments

Comments

@lsouchet
Copy link

This issue is a

  • bug
  • feature
  • question

Please describe the current behavior, and explain why it's bad.

I use a keeweb to manage my keepass db.
For services using SSO (Single Sign On), there are several urls that should correspond to the same entry (user, password).
On keeweb, such entries are filled with all the urls in additional fields.
On Tusk (and in CKP), when trying to log on one of those sites, the automatic search for entries does not find any close match. However when entering the website url in the "search entire database" I can find the desired entry.
So it appears that Tusk manages to find the custom field when using the "search entire database" feature, but cannot find it by itself.

Please describe how you think it should change.

In ideal use case, Tusk should propose the sso entry when logging to any website whose URL is referred to in a custom field.

Anything else?

@subdavis
Copy link
Owner

Solved in #85

Please see the readme: you want the TUSK_URLS custom field.

Please let me know if this solves your issue

@subdavis
Copy link
Owner

Closing due to no response.

@lsouchet
Copy link
Author

Thanks, I got it working!

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

2 participants