Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Not matching Subdomains
I have a set of logins that do not show up as suggestions when their sites match a subdomain.
You can see in the screenshot that I can search for a login with the website:
https://deploy-preview-1770--whoosh-staff.netlify.app/login
However, it does not show up automatically when I'm on the site:
https://deploy-preview-1837--whoosh-staff.netlify.app/login
Even though they differ only in their subdomain. Other sites seem to match correctly across subdomains. Is there something I should be doing differently?
14 Replies
Same problem here. All of our test sites on .cloudways or .wpengine or our own dev server show all of the logins for all the subdomains. we have shared vaults for the team and it lists all of everybodies login. yikes! For our test server thats high tens of logins. horrible. its ok for the first month and steadily becomes totally unworkable as the list builds up.
@kirsch Yes. Exactly!
This is driving me bonkers. It also doesn't seem from an outsider's point of view as something terribly difficult to implement.
Any or all of the following would be great:
- display subdomains in suggestions
- suggest subdomains first
- allow us to set a checkbox in the item that says "only match subdomain" or something to that end
I rely on 1Password to do a lot of development and I have a lot of subdomains with separate logins but different passwords... as I should. 1Password should simplify this best practice. The people most likely to run into this are also most likely to be your power users and most ardent evangelinsts.
Thanks!
Subdomain support has been talked about here since 2013. Is this support something that is being worked on? We use SSO at work and there are many URLs that get matched because they use the same domain name. (Sorry to hijack your post, cspeper) :-)
