How do I prevent 1Password from autofilling on specific urls?

2»

Comments

  • aquafarr
    aquafarr
    Community Member
    edited March 30

    +1 here, or +a team of 15 people.

    Saving your password for 1Password in 1Password seems like a terrible idea. Please find a way ASAP to block certain websites.

    The only close to workaround I've found as an administrator is this:

    In a vault that is shared with the entire organization create a log in with these settings:

    Login Title: x DO NOT save your log in for this site.
    username: Login Blocker (ask IT Admin)
    password: x

    (Don't put the term "1Password" or "Password" in the Login Title, this keep it from turning up in day to day searches of 1P. The password is literally one character. So that if it ever did get filled it would be obvious that the password is only one character.)

    website: https://1password.com
    website: https://my.1password.com/

    then do the filters for "Never fill on this website" for both.

    All this creates a pop up reminder team members to not attempt saving their PW to 1Password. This login is buried in a vault that no one would search out. But 1. admins can't lock editing of a Login so anyone could edit it and 2. I'm not sure how the conflict would work if they attempted to create a new password for this same site from within the app. There would be two instances of the website in the 1Password database, one blocked one not. For that matter a team member could still save their PW in 1Password they just can't fill it on a site.

    .... y'all just fix this please.

  • stellar292
    stellar292
    Community Member

    I'm also looking for a way to stop 1Password from showing autofill suggestions only on specific sites (e.g. RailsAdmin in several different environments). "Hide on this page" is only temporary, I'd like it to be permanent.

  • tygital
    tygital
    Community Member

    +1 here + a team of 3.

    Please implement this, as @YvesRausch wrote:
    "It is quiet simple: Add in context menu > Don't use 1Password on this site, add to blacklist, all be happy."

  • Unknown
    Unknown
    This content has been removed.
  • Dave_1P
    Dave_1P

    @aquafarr

    Can you clarify why you'd like to avoid having your team members save their account password in 1Password? This is something that is done automatically for accounts with the creation of a "Starter Item" item which is safe and secure. In fact, saving your account password for 1Password in 1Password can help protect your team members from phishing attacks since 1Password in the browser will only fill the account password from the Starter Kit into legitimate pages: How the 1Password Starter Kit Items Keep You Secure

    That being said, I've passed everyone's comments and requests for a permanent way to disable 1Password in the browser on certain pages along to the team. Thank you for the feedback.

    -Dave

    ref: PB-40568557
    ref: PB-40568463
    ref: PB-40568549
    ref: PB-40568569

  • alexhamer
    alexhamer
    Community Member

    Adding my voice to this request, i use a CRM which we absolutely need 1Pass to remember the login as it is complex and changes regularly, but once we're in we don't want it prompting every time we open a client record, because we can't read the client's address as 1Pass is in the way.

    At the moment i get 1pass popping up in every field on the client record on urls like www.website.com/clientdata/12345, so i would like to disable it for every path beyond /clientdata/

    Currently, i can turn it off using the icon in the data field, change windows to check our accounts system then when i come back, it is enabled again, it's very annoying!

    Please help!

    TLDR: I want to use 1pass to get in via www.website.com/login, but once we're in i want to disable it using a Path rule, and this is not possible as far as i can tell

  • lumiere
    lumiere
    Community Member

    Hi, I'm joining the queue in this thread to complain about the autofill malfunction.
    This is an issue that 1Password has been carrying for a long time, and I believe it's time to provide a response to the customers who pay for their subscriptions meticulously but for whom there is still no solution.

    In reality, the problem to solve is quite simple. I understand that you want to use the domain name for filtering, but I think you should give users the option to choose the type of filtering:

    domain name

    or

    text string or url "call it whatever you want, in the end, it's just a simple string of text"

    The autofill, if it finds the autofill set to a text string or url value, will perform a simple comparison.
    Does the page contain this URL? If yes, it does not perform autofill; otherwise, it does.

    Delaying the solution to this poorly designed feature, I don’t think, can even be attributed to the number of URL variables that a user inputs because, let’s be honest, I don’t believe the average user has more than 30 or 50 items with custom URLs. Normally, when an item is saved, the first URL entered is then used. This applies to 99% of the items saved in the vault.

    Providing the ability to execute a filter based on a string/URL more complex than just the domain name is an important feature.

    It's been years since the first complaints about this issue. When do you plan to solve it?