Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Firefox & Chromium on Linux Issues with windows.cloud.microsoft
This has been annoying me so much lately I had to post something about it. When working in an azure virtual machine with a browser that has the 1Password extension enabled the extension is detecting a password event for some actions I do within the virtual machine which aren't password related. I'm working off Linux but I'm sure it would happen on a wintel box as well. Triggers for this behaviour I've encountered so far: Entering a UNC value into the file explorer address bar Entering a search term or URL into a browser address bar Entering text into a search provider like Bing As you can imagine this is pretty annoying when you're trying to get work done. If I could also suggest that if you are targetting MSPs you want to detect which username the user has picked when doing an auth with O365/Azure and give them the appropriate password, as they will have a LOT of O365 accounts.
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 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?
Help with 1Password SSO Unlock Across Multiple Desktops
Hi, I’m looking for some assistance with 1Password in a small office environment (around 45–50 desktops) that runs Hybrid AD. We’ve enabled Unlock with SSO, and it works fine on a user’s first workstation. However, when the same user signs in on another workstation, 1Password prompts them to transfer their encryption key. The challenge is that our users often move between desktops throughout the day depending on their work schedule. This constant key transfer prompt is disruptive. Is there a way to disable this key transfer requirement or a recommended best practice to allow seamless use of SSO across multiple desktops? Thanks in advance for any guidance!
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.Research opportunity: Help shape the future of 1Password + gift card for your time
Hey 1Password community 👋 Our team is running 1:1 research interviews with current 1Password Business customers, and we’d love your insights. We’re especially interested in hearing from folks using the 1Password Enterprise Password Manager (with or without 1Password Device Trust or Trelica by 1Password), and who are involved in managing access, identity, and device posture at their company. Our goal with this research is to better understand how access is managed in the real world, especially in places where SSO, IdPs, and MDMs may not reach. Your feedback will directly influence how we evolve our products and features going into 2025. Who we’re looking for: Admins, IT, or Security leads at companies with 500–3,000 employees in North America, Europe, or Australia Decision-makers, or those with hands-on experience managing access tools Current users of 1Password Business and/or Extended Access Management What to expect: A 60-minute live interview Flexible scheduling between August 4th and 15th A $100 gift card from popular retailers as a thank-you We only have 10 slots available, so if you’re interested, please fill out this short screener survey. Thanks for being part of the community, we’re excited to learn from you!
Migrate users to Azure AD - Expiry
Hi, We are starting to move our users from password/recovery kit to Azure AD integrated. This has been going fine and we started by using a AD security group to provide the access. We had planned to use this group moving forward as we roll people onto the Azure AD SSO/SCIM, but it appears that the migration expiry date of the group is a fixed date from when the group was added. I would like not to have to create a new group as I migrate users, but I also don't want to move them all in a hail-mary fashion and add them all to the group now. Is there any way to change the migration expiration date? It appears that I can only set the maximum time as 30 days. I'm also afraid to remove the group and re-add this as it might invalidate the users who are already using the Azure SSO. Thanks for any information Jonathon Page
