Forum Discussion

Former Member's avatar
Former Member
4 years ago

Incorrectly retaining Secure Input

I haven't been able to determine exactly when this happens, but I've run into an issue where 1Password will cause Secure Input to be enabled, even after it's no longer active. (This would be mostly fine except it causes issues with programs like Keyboard Maestro and SteerMouse.)

I think it might start after filling on a webpage, when it prompts me to hit OK to fill the item? I'm not sure; I will update if I am able to figure it out any further.

1Password Version: 8.2.2
Extension Version: 2.1.3
OS Version: macOS 11.6

betas

5 Replies

  • Former Member's avatar
    Former Member
    4 years ago

    Hi @Smithjw, thanks for reporting this. I've added your report to our bug tracker. We'll be taking a closer look soon, and we'll let you know if this gets fixed in an upcoming release.

    If you have further feedback or need help, please don't hesitate to reach out :)

  • Former Member's avatar
    Former Member
    4 years ago

    @ag_Gabriele Not sure if this is related but I'm seeing this issue daily in macOS Monterey running 1Password 8. It seems that if I've edited an item in my vault, saved, then moved onto something else, when 1Password eventually locks and is waiting for me to enter my password (even while in the background) SecureInput is enabled. This causes apps like Logitech Options, BetterTouchTool, & Karabiner Elements to all stop functioning/remapping keyboard shortcuts as SecureInput is enabled.

    The solution so far is to remember to close the main 1Password window and not just background. It would be great if SecureInput could be disabled when 1Password is in the background/not in focus.

  • Former Member's avatar
    Former Member
    4 years ago

    Thanks! Please let me know if you run into it again. What do you use to check if Secure Input is enabled?

    In previous testing Secure Input would always get disabled when the app moved to the background, but maybe there's a timing issue of some sort.

  • Former Member's avatar
    Former Member
    4 years ago

    Hi! I authenticate with Touch ID.

    Armed with the information you said, I tried various things to attempt to reproduce the effect manually, including (with Touch ID enabled and disabled) saving new logins, unlocking 1Password from the browser, editing a login in 1Password and quitting, and nothing caused the bug to occur. (It happened accidentally earlier today, though.)

    I will try to pay attention, and check regularly to see what might be triggering the issue.

    Besides that, is there any other information I can provide for you?

  • Former Member's avatar
    Former Member
    4 years ago

    Hello @timothymh, I recently worked on this feature. Would you be willing to share a bit more information to help us pinpoint this bug?

    Based on your description so far, it sounds like you are using the extension. When activating the extension, do you get a Touch ID prompt? Or do you have to enter your password on the desktop app's lock screen?

    We currently activate Secure Input only when a text field of any kind is focused within the desktop app. It might be getting stuck in the "on" state when you switch back to the extension.