Autofill... domain matching choices?!? O. M. G.

Thank you for your reply.
Sorry, it was a typo. The two urls are identical except for the numeric part. As you wrote, 1password shows the correct login as the first choice, but it still shows both. I was wondering if you can only see one login for each url

vidario I'm seeing two differences in the URLs you specified. One of them has host www.bankxyz.com and the other www.bankxyx.com. Unless that's a typo, 1Password should be able to tell these apart right away. If that's actually just a typo, and the only difference is in the path, then the "Improved Autofill Suggestions" found in settings will still be able to handle the differences in the URL's paths. Specifically, if your login item has a specific path and the page you're visiting matches that path, then the relevant item will show up first in the list.

Let me know if that makes sense and whether you have more questions :)

Gabriele

Hi! I really love this feature! Thank you!
I was wondering if there's a way to manage this case:
bank 1: www.bankxyz.com/apps/pib2/03191brand0/public/login
bank 2: www.bankxyx.com/apps/pib2/03417brand0/public/login
Any chance to differentiate the two logins?
Thanks again

wagnerone interesting, thanks for explaining. I wonder if the “archive” feature found in 1Password 8 would help your use case. Archived items remain perfectly intact for an indefinite time, but they never get suggested in the browser. Anyone in the team can access them at any point via the app.

Secondarily (although I know you mentioned you prefer not to edit existing items), 1Password 8 has a password history feature that lets you keep track of all the password a specific item’s ever had. You can see them by using the drop-down next to the password field. I imagine the workflow your team has is already fairly set, but I wanted to mention this possibility.

I’m curious if any of these approaches would work for you.

@ag_Gabriele Thank you for reply!

The Archive feature could be useful, yes. I never really understood what it might be used for. Right now it seems like, in our case, a "pre-Trash" area. We could reconsider (or, consider) how we're using that vs the trash.

I know all about the password history. ;) It's a thorn in my side and IMO a security gap to not let us "clear" that password history on an item. My issue with it is I often have the need to duplicate complex records with various unique data items in them, but I cannot do so because of the password history being forever retained in the record.

Anyway, it's not just the password we want to track for historical reasons, but all the notes, additional Section and field items we add throughout that records actual lifetime.

I'm on the beta channel and got the latest production release 1Password for Windows 8.9.12 (80912010) yesterday. Now the new beta settings for autofill behavior are gone. There is no possibility anymore to change the autofill behavior.

I already changed the behavior for some of my entries. Are these settings lost now? Or will they be available again as soon as there is a new beta build available? 🤔

Thanks 1P_Mitch now I know it's "working as currently designed" and i'll eagerly await this to make it to the Safari extension one day!

Thanks for trying out the new autofill behaviour setting, @petro ! The Safari extension doesn't have a beta channel, and its latest update is still in review, so it is still a bit behind in terms of supporting the new beta matching capabilities. Safari will catch up soon, and we will make sure the setting is respected everywhere it should be before we release to stable. Really appreciate your feedback and bug reports!

Oh and as a side comment, I was skeptical of 1p v8 months ago, and the direction 1p was taking with "enterprise" features. Now I absolutely <3 it, and can't live without the improvements... Well done across the board!

Ugh sorry for the duplicate posts. Browser content blocker was acting up...

@ag_Gabriele a few more specifics to help narrow this down:
MacOS Ventura 13.0.1
Safari Version 16.1

Extension:
Extension: 1p for Safari 2.4.1
Autofill: both settings on

Mac App:
1password: 1Password for Mac 8.9.12 (80912004)
Experimental Autofill Suggestions: Enabled

Vault Config:
Both items are set to "Only fill on this exact domain"

So I think I've got everything right, but both suggestions show up on each other's domains!

@petro the use-case you're referring to should be supported. Have you enabled improved autofill suggestions? You need to right-click on the 1Password icon in the toolbar, click Settings, then scroll to Autofill and enable that option. Plus, if you want improved suggestions in Quick Access too, you have to go to the desktop app's settings, navigate to Advanced and set "Experimental Autofill Suggestions" to Enabled.

The only other thing to check is that your items are configured correctly. You have two options. Using the Autofill behavior menu, you can set the two items to "Fill anywhere on this website" and they will still show up on both subdomains, but they should be prioritized based on which subdomain matches best. If you set them to "Only fill on this exact domain", you'll see them show up only on the appropriate domain.

Curious if you're still running into this after doing that. It might also be that you're running into one of the bugs we've already ironed out but not released to the beta yet.

Cheers,
Gabriele