Autosubmit keeps turning back on

System
System
in 1Password in the Browser
This discussion was created from comments split from: How to disable auto-signin feature?.

Comments

  • dyqik
    dyqik
    Community Member

    This feature keeps turning on, with a pop-up notifying me that "1password now signs in automatically", even after I have turned it off. Please stop auto-enabling it, as it prevents me from signing in to most websites that I use.

  • Dave_1P
    Dave_1P

    Hello @dyqik! 👋

    I'm sorry for the frustration. The "Sign in automatically after autofill" setting should not turn back on after you've turned it off in a certain browser profile. So that I can better understand the situation can you tell me the following:

    1. Which browser are you using?
    2. Are you regularly clearing your browser's cache/history?
    3. Is the setting turning back on in the same browser profile (if you use profiles)?

    I look forward to hearing from you.

    -Dave

  • dyqik
    dyqik
    Community Member

    I use two browser profiles (one work, one personal) across multiple machines and do not regularly clear by browser cache/history in Chrome - I am using the Chrome plugin. This settings change seems to happen when Chrome has been updated, but that might be coincidental.

    It would be better for this setting to default to off, so as to avoid the security risks inherent in automatically filling and sending passwords.

  • Dave_1P
    Dave_1P

    @dyqik

    Thank you for the reply. Even with autosubmit enabled, 1Password does not fill your login information into any website without your explicit action such as clicking on a login suggestion on the page.

    I use two browser profiles (one work, one personal) across multiple machines and do not regularly clear by browser cache/history in Chrome - I am using the Chrome plugin. This settings change seems to happen when Chrome has been updated, but that might be coincidental.

    Thank for for these details. I'm not seeing any other reports of the feature being turned off aside from cases where a user has cleared their browser's cache history (which is expected behaviour). Is the issue always random aside from possibly being related to a Chrome update? Or are there any steps that you can provide so that I can try to reproduce it on my end?

    -Dave