AutoFill not working with exact match

I am using the latest beta versions of 1Password 6 for Windows, and the Chrome extension. I have tried the latest stable (non-beta) versions as well and that did not make a difference. I am having issues with 1Password always popping up Mini and asking me to make a choice after hitting Ctrl+\ instead of autofilling credentials, even when there is an exact URL match.

For example, I have stored in 1Password separate entries, each with one of the following URLs:
https://sub.mydomain.com/login
https://mydomain.com/somepage
https://othersub.mydomain.com/login

When I go to https://sub.mydomain.com/login and hit Ctrl+\, I get the Mini prompt with all three items listed. My understanding from reading other posts and docs (and common sense) is that 1Password should autofill credentials directly if there is a single exact match. I also understand that matching should be done across all URLs in an entry, such that if I have a single entry with two URLs and go directly to either URL, it should directly autofill. None of this is happening.

I have read about a "Lenient URL matching" feature which appears to have been renamed at some point to something about similar domains. I do not have any option like this in the Browser tab of 1Password settings. Help?


1Password Version: 6.6.046d
Extension Version: 4.6.5.2 (Chrome)
OS Version: Windows 10
Sync Type: Not Provided

Comments

  • matthew_agmatthew_ag 1Password Alumni

    Hi @mh4ll,

    Thanks for writing in and welcome to the Forum. 1Password for Windows 6 is still playing catch up on features at the moment as it was re-written from scratch and one of those features is being able to match subdomains to specific Login items if you have more than on Login for a single domain. The simple answer is that it's not done yet but you can look forward to seeing it in a future version of 1Password. Sorry about the inconvenience of this.

    I hope that helps. Please let us know if we can be of further assistance.

    Best regards,
    Matthew

This discussion has been closed.