It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Improve speed of login - Feature Request
Howdy all, As someone that has multiple SSO accounts on my machine (for various different purposes) one thing that has always added an extra step for my team, myself, and various users across our business, is that they have to click to select which SSO account they wish to log in with after clicking to SSO. We particularly use Entra SSO (so unsure if there is something similar for other providers) but would love to see 1Password leverage the login_hint parameter as described here https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sso This would mean that when you press to SSO with Microsoft, it would pass the login_hint parameter with the SSO username over, so if you have multiple logged in accounts, it will auto-pick the correct one. In theory a REALLY simple fix, but would save an extra click for every SSO sign in for affected users. Looks with big round puppydog eyes. Cheers, Stuart
1Password keeps asking for password instead of using biometrics
I use 1Password on both Mac and Windows systems. On these systems, I can no longer unlock 1Password from the browsers with a Mac fingerprint or Windows hello. It will ask for the fingerprint/hello, but then that won't work and I'll have to enter my password (again). I am seeing this behavior on multiple browser implementations (ie Safari, Chrome, Firefox) and, as stated before, on both Windows and Mac. The behavior seems to happen when I am opening the app too. I have updated the browser plugins on both systems to no avail. I am running version 8.10.78 on my Mac; I'm not sure what is on my Windows system at this time. This behavior started for me about 3 weeks ago. Previously, the biometrics would work to unlock 1Password on the browser after I had entered the password somewhere else.
Okta MFA codes stored in 1Password
Hey all, I ran into an issue when integrating 1Password with our IdP Okta, a good amount of our users use 1Password as a means to store their MFA codes, including Okta. This meant that when the users tried to login to 1Password, they found that they could no longer access the MFA code for Okta to login to 1Password. And that left them stuck in a loop, need Okta MFA code to login to 1Password, can't login to 1Password sine they need the MFA code. Is there a solution for this other than asking users to use another MFA method for Okta? We don't provide company mobile devices, and our company is fully remote meaning some labour laws restrict me asking our users to install another MFA app (like Okta verify) on their personal devices.Feature Request: Better multiple account unlock
Hi All, So right now, in order to have both a personal and work account unlock simultaneously, you have to set the master password to the same for both. This creates issues if your personal account master password isn't strong enough, and also just feels... icky. reusing the password. Would be nice to see the ability to save work account password in personal account, then tell 1password to automatically unlock the work vault with those credentials.
1Password for Windows app keeps requiring encryption key transfer
I have a business account that uses SSO for authentication. I am able to authenticate in the browser just fine and use the browser extension with no issues. When I sign in to the Windows app via SSO, I am asked to transfer the encryption key from my browser. I am able to do this successfully, but I keep having to transfer the key every day or two. Is there a way to prevent the encryption key transfer from happening or to get it to stop repeating?When should we expect a fix for prompting for Hello credentials after unlocking with password?
There is a long-standing (many months so far) bug where Windows Hello is triggered after unlocking a vault via the password. 1P support reviewed and verified this is a bug back in November 2024 on QFB-16867-382--1P should not prompt for Hello if the vault was unlocked via password. Is a fix already expected for this? If so, when? If not, can it please be prioritized? Thanks in advance,
