Skip to main content
November 7, 2024
Question

Wildcard implementation in website property of Login Item

  • November 7, 2024
  • 20 replies
  • 2453 views

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 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

20 replies

April 17, 2026

+1

I have the same use case as well.

1P_Dave
1Password Employee
1Password Employee
April 21, 2026

Thank you for the feedback! 

-Dave

CFP-19421

July 7, 2026

+1 would be so so helpful to test dev links!! (e.g. *.vercel.app) 

1P_Gem
1Password Employee
1Password Employee
July 10, 2026

Hi ​@meg-air, thanks for letting us know you’d like to see this as well! I’ve filed your feedback with the team.

August 15, 2026

Adding my +1 as well. We use an internally self-hosted instance of Okteto tied into our CI, and preview environments get similarly ambiguous URLs like container1-app1-mr-123.dev.example.com.