Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
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?
1Password Identity Provider Migration Tips
Hello, My company is currently utilizing Cisco DUO as it's sign-in identity provider. I am taking the charge in migrating our systems over to using Microsoft 365 SSO rather than 3rd party systems. This includes migrating 1Password over to Entra ID login. 1Password has a great documentation on how to setup a new identity provider, but I was hoping to see if anyone had any tips on migrating between identity providers (Cisco DUO --> Microsoft Entra ID). My current understanding is that, once I disable the Cisco DUO connection, all non-owner users will be required to setup a password and download their Emergency Kit using the recovery process. Then once the Entra ID connection is made, all users will then be prompted to login again using their Microsoft accounts to register with the new identity provider. Is there any way around this process to make the migration smoother? Additionally, does anyone know if you are able to test the connection with the new identity provider before de-activating the current one. I'm just looking to reduce the downtime on my users. Hoping someone smarter than me has some answers. Thanks!
Assistance Needed: Users Unable to Access 1Password After Sign-In Method Change
We recently switched our sign-in method to Microsoft, but several users did not complete the 1Password setup process within the 30-day window and are now unable to log in. Performing an account recovery doesn't work. What is the recommended process to resolve this and restore their access?
SSO in Edge giving me error 400
I've been running 1Password using Azure SSO authentication for some time now and it's been going relatively smoothly. Yesterday I had one user complain they were getting the following 400 error: I've done troubleshooting for this user and we've found that when they are signing in through Chrome (their secondary browser) then it will sign in fine, but signing in through Edge or trying to recover their account through Edge results in this error. I can't put my finger on what could be causing this although I have a feeling it's something quite simple. Has anyone else had anything previous and can advise? Many thanks in advance.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!
User account still active in 1Password even though disabled/deleted in Okta
Hello everyone, we recently found out we still have an active user in 1Password that was created using User Provisioning through Okta. Now, the user has since been disabled and deleted in Okta, but in 1Password it still shows as active. How can we disable the user in 1Password? I can't find an option for that.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.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!
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
