You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
This issue is a
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?
The text was updated successfully, but these errors were encountered: