Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Help with Auto-fill to work with Page Paths rather than subdomains?
Hello,
Our company is struggling with the Auto-Fill tool for websites that uses paths. Here's an example of the issue we are having:
Our phone system site has two login pages, one for regular...
Has any progress been made on this? I am just trying out 1Password coming from Bitwarden and one of the features I really like about Bitwarden is the flexibility in deciding what URI/URL it matches against. Here are some of the scenarios I've used with Bitwarden that don't seem to work with 1Password.
1) Subdirectories (as mentioned above) so different credentials for example.com/serviceone than for example.com/servicetwo.
2) Ports, example.com:8443 having a different login than example.com:9443. While this one doesn't come up much on the public Internet, I see it in development and test environments when multiple services are running on a single server so must run on different ports. The one example I can think of where I see this not in development is with VMware's vCenter. The main vCenter web interface runs on 443 whereas the appliance management web interface runs on 5480.
I would love to see at least these two options added to 1Password, but if the greater flexibility that Bitwarden provides would be made available in 1Password, that would be great.
- 1P_Dave
Moderator
Thanks for reaching out! You can configure 1Password to only fill when a certain domain (including the port) is an exact match (you'll want the "Only fill on this exact domain" option): Change where a login is suggested and filled
Autofill behaviours won't distinguish between different subdirectories, only subdomains, so you'll still see the login suggested on both example.com/serviceone and example.com/servicetwo. I'll pass along your request for more control over filling on different subdirectories to the team and they'll consider adding such a feature in the future.
-Dave
FWIW, I was just looking for this same functionality – i.e., being able to restrict a password based on path. In my case, we have an application that uses a single sign-on with Keycloak. Each environment (dev, qa, staging, production) use the same domain (sso.example.org) to authenticate; however, they could be distinguished based on the path (sso.example.org/realms/dev/... vs. sso.example.org/realms/staging/...).
I expected the 1Password's autofill behavior of "Only fill on this exact host" to match only URLs that started with what I provided, including the path – e.g., using this option for "foo.acme.com/bar/" would match any URLs starting with "foo.acme.com/bar/"). I was disappointed to find the path is ignored.
So, here's another vote to change change the autofill behavior option from "Only fill on this exact host" to "Only fill on this at this location" (and include any provided path as part of the filtering). It would make the feature both more intuitive and useful, IMHO.
- 1P_Dave
Thank you both for the feedback, I've shared it with the team.
-Dave
PB-52097641
