Forum Discussion

bedilbek's avatar
bedilbek
New Contributor
5 months ago

Wildcard implementation in website property of Login Item

website property inside 1Password Login Item is a great feature which helps to automatically detect and auto fill username and password into the form fields. What's great about it and what's already implemented:

  1. You can actually create multiple website properties and still any of the matching websites will work
  2. You can set the domain to the website property and any subdomain of that domain will work
  3. You can set the domain to the website property and any subdirectory of that domain will work

However I can give an example from netlify (web deployment platform) which won't match with any of the above 3 features. Let's assume I am developing web application and I set my application url as https://some-app.netlify.app. Netlify has a greate feature to customize subdomains based on the different deployment strategies. For example if I am now working on new github branch and I create a PR #100, then Netlify automatically creates new deployment url https://deploy-preview-129--some-app.netlify.app which is not just a subdomain of netlify.app because there can be thousands of app in netlify, however this is slightly different customized subdomain of netlify with some predefined prefix.

So what I would I like is implementation of some custom wildcard options for the subdomains like *sub.domain.com where I can have potentially anything in the place of wildcard *.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

browser extension
feature request
  • fabianerni's avatar
    fabianerni
    New Contributor
    4 days ago

    We have the same use case, that we use subdomains for feature deployments in our staging environment. Wildcards in website URLs would help a lot

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    5 months ago

    Hello bedilbek! 👋

    Thank you for the detailed explanation! I can definitely see how wildcards for autofill behaviour rules would be useful in the case of Netlify and, while I can't make any promises, I've filed a feature request to have our product team look into this further.

    I appreciate you taking the time to send in your feedback. 🙂

    -Dave

    ref: PB-44282690

    • blkist's avatar
      blkist
      New Contributor
      2 months ago

      I also would greatly benefit from this feature! I work at a company that has over 5000 network devices that we have to manage. We access them using their IP addresses. (eg. 10.x.y.z) We use LDAP integration on all of these devices, so that each of our team members use their own AD login for each device. I have my AD credentials stored in 1Password with about 100 different websites (IP addresses) associated with that login. If I want 1Password to autofill that credential into each of those devices whenever I login, I have to edit the login in 1Password and add that IP address to the webites list. Sure, I could keep editing the list every time and eventually have a list of 5000 websites under that single login in 1Password, but it would be nice if I could just put a single website under that login that looks something like (https://10.*) and have the asterisk be a wild card so that every network device would ask to use that login.

      Please add me as a second requester for this feature request!