Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
Forum Discussion
MNWardrop
3 hours agoNew Member
Extension Gets Stuck Saying "Unlocking..."
Within the past week, most of the users at our company have started experiencing an issue with the 1Password browser extension in both Chrome and Edge.
After signing into the extension using SSO, the extension icon changes to show that it is unlocked — the lock icon disappears — but when the user clicks the extension to open the menu, it gets stuck on “Unlocking…” and never fully opens.
We have found a temporary workaround, but it is inconsistent and not practical for regular use:
- Click the SSO button to unlock 1Password.
- After the SSO tab opens and closes, immediately click the 1Password extension again before the lock icon disappears.
- The extension briefly still shows the SSO button, then successfully unlocks and displays the menu.
However, this only works temporarily. If the user tries to open the extension again on the same browser tab, it goes back to being stuck on “Unlocking…”. If the user switches to a different tab before opening it again, it appears to remain unlocked for the time being.
This is affecting both Chrome and Edge. So far, the few users we have who are using Firefox do not appear to be affected. However, most of our users do not have have access to Firefox, so switching browsers is not a practical workaround for us.
This also seemed to start around the time Chrome updated to Version 147.0.7727.102, which resolved the previous 1Password-related issue we were seeing, but this new issue started occurring afterward.
Current versions in our environment:
- Chrome: 147.0.7727.103
- Edge: 147.0.3912.86
Also worth noting: we do not have the 1Password desktop app installed on our users’ computers. They are using only the browser extensions.
Has anyone else started seeing this behavior recently, especially in Chrome or Edge with SSO-only extension usage? Are there any known workarounds, policy settings, extension settings, or browser flags that may help resolve or mitigate this?
No RepliesBe the first to reply