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

I just tried the new settings, and saw it couldn't differentiate between:

company1.my.salesforce.com
company2.my.salesforce.com

A setting that allows it to be filled out for the exact FQDN would be helpful. Or am I missing something?

+1 for this. I just tried the new settings, and saw it couldn't differentiate between:

company1.my.salesforce.com
company2.my.salesforce.com

A setting that allows it to be filled out for the exact FQDN would be helpful.

+1 for this. I just tried the new settings, and saw it couldn't differentiate between:

company1.my.salesforce.com
company2.my.salesforce.com

A setting that allows it to be filled out for the exact FQDN would be helpful.

@andmade if you're referring to the 1Password popup that you can access via the browser toolbar, you're right, that seems to be an oversight on our part. I've tracked this bug and we'll see about getting it fixed in the upcoming betas.

Let me know if I can help with anything else :)
Gabriele

For the new autofill choices, I noticed the exclusions only take effect on the dropdown box (so the other ones you told not to show up still show up in the extension popup). Is it possible to have it also take effect on the extension popup? That's what I normally use for filling via a keyboard shortcut rather than the dropdown (which has the autoshow option turned off).

@ag_Gabriele

Just thinking through this, I wonder if those two things would be mutually exclusive in your perception? I.e. are there situations where a hypothetical "don't show suggestions on this website" option would be useful and where the existing "Never fill on this website" wouldn't, or vice versa?
Sorry, I missed that comment ... 🤔

Yes, there are situations where I would love to have an option for Don't show suggestions on this website. On my banking website, I don't want to use autofill. Normally it looks like this:

But the suggested credential is the password only for the app version. So, I'm not able to use it either here on the website.

When switching the autofill behavior to Never fill on this website in this entry, the credential is not suggested. But the suggestion popup is still available.

That's where the possibility to disable suggestions on the website makes sense. And for such an option, a long awaited feature request should exist already. 😉

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.

Cheers,
Gabriele

Thanks for the update, @ag_Gabriele

We rotate passwords on a regular basis for many app stacks we manage and just got into the habit years ago of making new records every time we do this so we can keep all the old records intact as a set with whatever historical references the records accumulated throughout their lifetime. We want the records to exist in perpetuity, but we don't want them polluting our teams form filling options.

Ever since we switched to v8 all our developer, devops teams, etc. where we used to have a single entry pop up to fill a form, we now have like 20 records show up for every site we log into countless times a week to work on things because that v7 attribute is not honored. It's enough to drive a person mad.

It was suggested we use different vaults, hide them, etc., but that is as disruptive a change as having to deal with this in the short term. We're a busy team, we already maintain too many vaults as it is, and it would be a paradigm shift to deal with.

wagnerone we looked into whether the 1Password CLI could help with your setup but currently we don't support the sort of advanced editing that would be required to control those specific options. I'm afraid there's no quick workaround in this case, but as I said we've added this to our list of work to do and we will get around to it in the future. I can't promise a timeline unfortunately, we'll be very busy with other priorities until late in the year.

If you have any extra information about your workflow (without revealing anything personally identifiable please), it would be useful to know why you were using that option. Specifically, I'm curious to know more about why you prefer to set the display option rather than remove the problematic URLs from the item. I realize those are not equivalent and I imagine the reason lies somewhere in there, but curious to hear the full story either way :)

Cheers,
Gabriele

@1Passworder1 hey, thanks for the feedback! That's something we've been working on and you should see it in one of the upcoming betas. It will look something like this:

We're always open to hearing your feedback!

Cheers,
Gab