Request: Improvements to autofill behaviour (option to restrict to port or sub-folder)

Question

Please improve the filtering options in 1Password for where a login is suggested and filled.

Currently, as outlined https://support.1password.com/autofill-behavior/, it possible to restrict autofill to:

Autofill at a specific domain. e.g. https://mydomain.com
Autofill at a specific sub-domain (and not the domain). e.g. https://here.mydomain.com and not https://mydomain.com

Please could you add two more options:

Autofill at a specific port ONLY for the specific domain. e.g. https://mydomain.com:8625 or https://here.mydomain.com:8625 or https://192.168.1.49:8625 (autofill only shows at this specific port at this domain and the regular logins to the main http (80) and https (993) sites are not displayed). I have a local server, with a single IP address, but with multiple sites all at different ports. I hate that they all get suggested for each site, when the login is only needed for the site at this specific port. It gets really confusing.
Autofill at a specific sub-folder ONLY for the specific domain e.g. https://mydomain.com/forum and not https://mydomain.com. Some websites use a seperate login for their customer forum versus the login for the main website, and it is not always hosted at a different sub-domain. Sometimes it is in a sub-folder to the main site.

patrick227 · Answer

Yes! This is especially true for the “new autofill experience” in the Chrome beta/nightly extensions: I am not sure if this experience is available yet with the stable 1Password release. But for websites that do not use a subdomain for a login, but rather a sub-folder, such as Wordpress websites, this is extremely relevant: Eg. www.[mywebsite].com now pops up with autofill when mywebsite.com/wp-admin and the redirect to https://www.[mywebsite].com/wp-login.php?redirect_to=https%3A%2F%2Fwww.[mywebsite.com]%2Fwp-admin%2F&reauth=1 - In this case, I would like to restrict the auto-fill to “https://www.[mywebsite.com]/wp-admin” and “https://www.[mywebsite.com]/wp-login.php” (not sure if the second one is needed for Wordpress, but I can’t troubleshoot triggers for subfolders since subfolders cannot currently be isolated for the login prompt.

I did try editing Autofill Behaviors and including just the website with subfolder, but it did not work as it was just applicable for subdomains.

Right now, it’s annoying to get any prompt at all to autofill when navigating to “https://www.[mywebsite.com]/” - the traditional auto-fill experience didn’t trigger anything like this since it was focused on login fields, and while 1Password might see a contact form and depending on the entry fields, might trigger an entry on a contact form, it didn’t pop up from the top of the page to fill when visiting the website.

I think supporting isolation of the autofill experience to sub-folders, not only subdomains, when we request it would solve the issue. But perhaps there also could be a way to opt to use the traditional auto-fill experience on a per-website basis? But I assume the first option would be preferred for 1Password, as the “new” autofill experience wording is indicative of it being a replacement that would replace the old experience.

I have this same issue with other websites where limiting the autofill prompt to a subdomain does not help with isolating logins, as some calendar management systems (calendar/booking/client creation) don’t use a separate subdomain for just the login; and calendars/booking/client creation/etc websites show many fields and so I’m running into the new autofill experience being a downgrade for these websites, as 1Password is constantly activating the login now: it wasn’t perfect before with the traditional auto-fill experience, and so for both types of experiences, isolating website logins to specific pages could really help.

Thank you!

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO