Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
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:
- You can actually create multiple
websiteproperties and still any of the matching websites will work - You can set the domain to the
websiteproperty and any subdomain of that domain will work - You can set the domain to the
websiteproperty and any subdirectory of that domain will work
However I can give an example from https://www.netlify.com/ (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
17 Replies
+1
I have the same use case as well.
- 1P_Dave
Moderator
Thank you for the feedback!
-Dave
CFP-19421
+1 to pile-on! In our case our devleopers dynamically create sites based in github issues so we end up with n varations of local test domains that need credentials which are the same in every case, and follow this pattern:
{projectName}-{githubIssue#}.test
ie
superdevproject-1001.test
Would be super if you could add this to something like
https://superdevproject-*.test for the website property. :)- 1P_Dave
Thank you for the suggestion, I've filed a feature request on your behalf!
-Dave
CFP-19421
+1 here too. We use 1Password for all our sites that have some level of federation and password login would be the easiest.
+1 This would really help our development team as we have multiple preview environments using the same credentials to log in.
+1 this would be huge...it would be amazing for IP ranges too. IE... 192.168.0.*, if all the devices in this subnet were the same type, ie. security cameras, UPS devices, iDRAC, etc, then it would allow for autofill.
- 1P_Dave
Thank you for the feedback! I've filed a feature request on your behalf as well.
-Dave
PB-50485933
- 1P_Dave
fabianerni, peterwcm, and hege
Thank you for the requests! I've filed your comments with our product team for their consideration.
-Dave
PB-48478112
PB-48478143
PB-48478151 +1 for this. This would make power users very happy and still would not get in the way of more casual users.
+1 for this. Pantheon also set up their feature environment domain using a new unique domain instead of subdomains. Examples:
pr-101-helloworld.pantheonsite.io
pr-200-helloworld.pantheonsite.iopr-777-another-site.pantheonsite.io
pr-377-another-site.pantheonsite.ioWe have the same use case, that we use subdomains for feature deployments in our staging environment. Wildcards in website URLs would help a lot
