Error when using 1Password in the browser: "Your session has expired."

Hi @timestamp and @sheath1 👋

I'm sorry that you are experiencing this issue in Vivaldi and Chrome, respectively. Our developers are currently investigating a few issues that may be related to what you're experiencing. To help us determine what's occurring in your cases, could you both confirm the following?

• Does your 1Password account have two-factor authentication enabled? If so, are you using Duo or Okta?
• Do you have the desktop app installed? ( @timestamp I see you've answered that you're not using the app previously, so you can skip this one)
• In the "Security" section of the extension's settings, do you have "Automatically lock 1Password" toggled off?

Once I learn more about the situation on your respective devices, I’ll be able to advise further on whether I’ll need a console log to dig deeper. Looking forward to your replies.

-Trevor

Hi @Trevor_1P,

I use Authy for 2FA, and have "Automatically lock 1Password" toggled off.

Thanks so much!

Hi @Trevor_1P

• Yes, I've got two-factor enabled using Google Authenticator.
• No I don't have the desktop app installed, I doubt I can on this box as it is enterprise managed.
• "Automatically lock 1Password" is toggled off.

Thanks for the assistance.
Shaun

@timestamp and @sheath1

Thank you both for the replies. It does sound like you're running into a known issue that our developers are investigating. There are two ways to workaround the issue until a permanent fix is released:

1. Turn "Automatically lock 1Password" on when using 1Password in the browser.
2. Install the desktop app. You can set your auto-lock preferences there using this guide: How to set 1Password to lock automatically

Our investigation has narrowed the issue down to a bug with how the auto-lock feature in the 1Password browser extension works, if the extension is set to never lock then authentication fails and a new tab with a sign in page is opened (as you've noted).

If you turn on auto-lock for the browser extension then the issue shouldn't occur. Alternatively, when the desktop app is installed authentication is handled by the desktop app and not the browser extension which avoids the issue as well.

Let me know if both workarounds don't work for you. We're hoping to release a permanent fix as soon as possible.

-Dave

ref: dev/core/core#27669

OK @1P_Dave , I've set the auto-lock feature on in the browser extension since I cannot install the desktop app on my corporate box. I'll let you know how that goes.

Just to add another data point, I'm having this same issue. 2FA with Authy, Chrome extension auto-lock set to off, and no desktop app installed. The problem with the request to provide the extension console log is that the instructions say to enable it and then reproduce the issue, but the problem appears periodically on its own, and I don't know what steps to take to actively reproduce it.

Well at least we have a workaround. Tying the password every 8 hours is better then typing it all the time.

@sheath1 and @krischik

Thank you, let me know if you still see the issue even with the workaround. We hope to release a permanent fix soon.

-Dave

@kipling

I understand that it can be difficult to send in a console log and I'm sorry that you're also seeing the issue. So that I can determine if you're affected by the known issue that I mentioned earlier, can you tell me the following:

1. Is two-factor authentication enabled for your 1Password account? If it it then are you using Duo or Okta or just another authenticator app?
2. Do you have the desktop app installed?
3. In the "Security" section of the extension's settings, do you have "Automatically lock 1Password" toggled off?

I look forward to hearing from you.

-Dave

@1P_Dave the workaround of enabling "Automatically lock 1Password" with an 8-hour timeout seems to be working. Thanks for the suggestion, and I look forward to a proper fix!