Add port number to URL filter for available logins


I run multiple services available over HTTPS on the same domain. Currently, I can save separate logins for the domain, but when I visit the login page for any of the services on the domain, all username/passwords are listed. It would be nice if the filter logic for which logins are presented based on the URL of the current page considered port number as well as domain.

More specifics. I'm running Jira, Jenkins, and Bitbucket in Kubernetes containers. All are accessible from the top level domain, as follows:

  • Jira is available at https://<domain>:<port1>
  • Jenkins is available at https://<domain>:<port2>
  • Bitbucket is available at https://<domain>:<port3>

I can store separate passwords for each, but when I navigate to the login page of any of the three, the list of logins presented when I access 1Password shows all three. It would be slightly more efficient if 1Password would display only the login that matched both the hostname and port, rather than just the hostname.

It seems unlikely to me that, aside from HTTP/HTTPS being on different ports, there would be a frequent occurrence that the same login/password would apply across multiple ports, but perhaps I'm not thinking broadly enough. If that is the case, perhaps a preference option that allows the user to list domains that should treat port as part of the login definition? Granted this is not likely to be of use beyond developers, but based on some of the group discussions in my company, there are a lot of developers who use 1Password.

1Password Version: 7.2.2
Extension Version: 7.2.2
OS Version: 10.14.2
Sync Type: Not Provided


  • brentybrenty

    Team Member

    I edited your post to fix the URLs. Since you used pseudo-HTML tags, hey were hidden and didn't make sense to me until I looked at the "source". ;)

    I can definitely see how changing 1Password to work that way that would be useful to you and others with a similar workflow. We sometimes get requests for subdomain- and even full-URL-only matching too, so I'm not sure what the right answer is. We don't want to complicate things unless the benefits outweigh all the costs. I don't think it's something we can prioritize over other work at this time since it is a bit of a niche use case, but it's something we'll keep in mind as we develop future versions of 1Password. Thanks for the explanation! :)

  • ggenterggenter

    Lack of this is one of the things that turned me away from 1password while evaluating it today. Since like original poster said, flexible url matching patterns are something that is really important for professional users. Bitwarden and LastPass have it. So if you want professional users then you should implement this.

  • BenBen AWS Team

    Team Member

    Thanks for the suggestion, @ggenter. :)


  • max_kmax_k

    lack of port number filters is indeed a huge turn down of user experiences. me and my friend were shocked when we find out that 1password can't even tell apart different ports (I mean for developers, that's pretty like basic demand, right? ). and I have noticed that there was a discussion of this way back in 2015, and one of your members noted that you have a feature request vote kind of case. ( that's a really long time. I am not sure whether I am able to see this feature being implemented while i'm still alive.. lol..

  • ag_michaelcag_michaelc

    Team Member

    Hey @max_k!

    We do take our users' feedback to heart, but I just want to clarify we don't have a voting system in place for feature requests. Speaking more generally, if the demand is high for something and it's realistic to implement, we will likely do so, but voting might imply that something needs x number of votes and then it's suddenly in a different category of prioritization for our development team, and that is not how it works. We take note of the volume, of course, but it's not a tally system. It may seem like a trivial distinction, but I felt it was worth expanding on in this case.

    At any rate, thank you for the feedback. We'll take it into consideration. :smile:

  • I am just started using 1Password, and I am very happy about it. But if flexible url matching patterns will be supported, I will be even more happy. Currently I get a long list with passwords for my domain(s) and if there is a filter for the port-number or subdomain this will be solved.

  • BenBen AWS Team

    Team Member

    Thanks for taking the time to share your perspective on this @jgjverheij. Glad to hear overall you're enjoying 1Password so far.


  • AlexNZAlexNZ

    +1, this feature would make my job a lot faster!

  • brentybrenty

    Team Member

    Thanks for letting us know it would help your specific use case. :)

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file