Forum Discussion

lumarel's avatar
lumarel
New Contributor
7 months ago

Improvements to website matching pattern

I'm trying to find a thread again, that was talking about further options how to improve the matching of websites/the autofill behavior.

I remember that I described there, how it would be helpful to have a glob matching or regex pattern matching. Coming back to take a look for the progress, but it seems this thread disappeared.

Thanks and cheers, lumarel

community feedback

6 Replies

  • uncaught's avatar
    uncaught
    New Contributor
    1 month ago

    This is getting ridiculous :(

    Can I please have pattern matching? Thank you!


    And no, my shellys don't each need a different password.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      1 month ago

      uncaught​ 

      Thank you for the feedback. Can you tell me a little more about the website addresses that you're adding to the Login item? If you just add a single website address with "local.com" (no subdomain) then that item will be suggested on all of the different subdomains as long as the Fill anywhere on this website autofill behaviour is selected: Change where a login is suggested and filled

      Is there a reason why you're adding each subdomain separately? 

      -Dave

      • uncaught's avatar
        uncaught
        New Contributor
        1 month ago

        Hey Dave,

        that is a local domain namespace. All my local infrastructure has a domain like "something.local.mylastname.tld".

        So there are more domains like that, where I definitely have different passwords. It's just that all my shellys (smart switches) don't need different passwords.

        Another use case is at work where we also have local domains with various sub domains. A common pattern there is when we deploy our software to test slots, each having the same test users/passwords, too. So a pattern like "something.slot-*.local.company.tld" would be appreciated there, too.

  • bmamlin's avatar
    bmamlin
    New Contributor
    2 months ago

    If we can't have regex path matching for advanced autofill behavior, could we at least change the autofill behavior option from "Only fill on this exact host" to "Only fill on this at this location" (and match anything that begins with the provided URL, including any provided path). This could cover both restricting to (sub)domain and/or path. It would make the feature both more intuitive and useful, IMHO.

    Example use case: single sign-on with different environments (dev, staging, prod) that use different credentials all use the same (sub)domain and are distinguished by path (e.g., realm in path).

  • 1P_Timothy's avatar
    1P_Timothy
    Icon for Community Manager rankCommunity Manager
    6 months ago

    Hi lumarel​! Thanks for writing in. 

    The thread that I believe you're referring to was older and didn't make the cut for migration. As for glob matching, regex matching, or other advanced URI/URL matching options, we don't have any updates to share at this time, but I can confirm a request was submitted on your behalf. 

    I suspect you're aware, but I did want to share our guide covering the autofill behaviour options that are currently available. They may not cover the sort of use case you'd want regex matching for, but can still be quite helpful. 

    Let us know if you have any questions, and thanks again!