pgp signature not trusted
I upgraded PGP signatures: $ curl -sS https://downloads.1password.com/linux/keys/1password.asc | gpg --import gpg: key AC2D62742012EA22: 3 signatures not checked due to missing keys gpg: key AC2D62742012EA22: "Code signing for 1Password <codesign@1password.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 But during checking 1password-cli source, I got: gpg: Signature made śro, 28 maj 2025, 12:15:49 CEST gpg: using RSA key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 gpg: Good signature from "Code signing for 1Password <codesign@1password.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 3FEF 9748 469A DBE1 5DA7 CA80 AC2D 6274 2012 EA22 Is something wrong with your PGP signature? I'm worried about whether the 1Password code is secure.Solved22Views0likes4Comments2FA support on Ubuntu
My wife has fingerprint-reader support to access 1Password on her Mac. Is there a way to do the same on my ThinkPad, currently running Ubuntu 22.04 (although could be upgraded, if that helps)? I have not been able to find stable support for the fingerprint reader on this machine, and I don't know if 1Password would support it. Integration with the 1Password Firefox plugin is the key. I would be willing, might even prefer, using a an external fingerprint reader, if this would work.13Views0likes1Commentrpm gpg key expired
Hi, I followed the instructions for verifying the signing key https://support.1password.com/linux-trouble-updating/#check-if-your-signing-key-is-valid Every attempt I've made says the key is expired. Are you sure you've signed it and updated the expiration? If so, what extra steps are needed? Here's the key output with the same key fingerprint but the key is expired ``` pub rsa4096 2017-05-18 [SC] [expires: 2032-05-16] 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 uid [ unknown] Code signing for 1Password <codesign@1password.com> ```Solved59Views0likes1CommentAdministrators, get a sneak peek at the new sidebar
Starting this month, we’re rolling out a redesigned admin sidebar to create a more consistent and intuitive experience across 1Password products. We’d love your feedback to make sure we’re reaching that goal. Note that this change will only apply to administrators using 1Password for business. What’s changing? Sidebar location: The sidebar has been moved from the right side of the screen to the left side so it's more consistent with the 1Password apps. Improved navigation: Each section of the sidebar now has an icon and we've improved the organization of the pages with tabs. Product switcher: If your team also uses Kolide or Trelica, you can easily switch to those products from the menu in the top left. What’s the timeline? April 23–May 7: Admins will see an in-product banner inviting you to try the updated sidebar. May 7: The new sidebar becomes the default experience for all accounts. Can we switch back? Yes – if your team prefers to stick with the existing sidebar for now, you can revert to the old design through your settings during the early access period. Here’s how: Select your account name in the top right, then select Manage Account. Toggle “Admin console design updates” off. Please reply below with any thoughts, ideas, or questions! Your feedback is invaluable in helping us continue to improve 1Password.151Views6likes2CommentsVault Naming Convention – Security & Usability Concern
The recent decision to name all core vaults as "Employee" in 1Password is highly counter-intuitive and introduces unnecessary risk. In environments where multiple 1Password accounts are used, we've observed that users frequently misplace credentials in the wrong "Employee" vault. As a result, sensitive data—including API keys, passwords, and banking details—has been inadvertently exposed to unintended users with access to these vaults, despite the correct Primary Vault being set. This naming convention creates significant ambiguity. Why wasn't a more logical format such as "$AccountName - Employee" considered to differentiate vaults across multiple accounts?Solved111Views0likes3CommentsHelp Shape the 1Password Admin Console
Calling all Enterprise Password Manager and Device Trust admins! The product team at 1Password is excited to invite you to join our usability sessions to test out a new navigation experience in the 1Password Admin Console. As a participant, you’ll get early access to the new design and a chance to work directly with our team to improve usability and enhance discoverability for admins managing multiple products and capabilities. Sign up here if you are interested! Spaces are prioritized for B2B 1Password Admin customers, so if you’d like to be part of this, let us know soon!52Views0likes0CommentsMicrosoft SSO does not work in Linux desktop client
We are introducing Microsoft SSO at my company. Unfortunately I can not get the flow to work with the 1password Linux desktop client (on Ubuntu 22.04.4). I logged out the desktop client and then tried both "Sign in on 1password.com" as well as "Enter account details". Both at some point take me to the web browser, where authentication seems to complete successfully at which point the browser prompts me asking if I want to allow xxx.1password.com to open the xdg-open application. When I confirm (click "Open XDG-open") nothing happens. I suppose at this point the web flow tries to redirect back to the app using a custom URL scheme but it seems that the handling of that custom URL scheme is not properly registered with the OS. I updated to the latest client version in the process (was in the 1-before-latest before), also hoping it might fix any missing custom url scheme handling, but that didn't change anything. Then to make sure the problem isn't with some specific misconfiguration of my OS I made a clean life USB stick with the just-released Ubuntu 24.04 LTS to try it there, only to discover that the 1Password application simply crashes immediately on start-up on that, so I guess that's a little something to look into as well. In the end I did manage to get the client authenticated with some hacking: using the Chrome developer tools to intercept the custom-url-scheme URL the flow is trying to open (from the redirect response) and then just running 1password from the command line passing that URL as an argument, which let me complete the flow. But there does seem to be a bit of an issue there that you might want to look into. BTW, it looks like there is supposed to be some kind of fallback in the flow. Where it says "If you don’t see a prompt in your browser, try again.". And after trying again the link changes to "Still not working", after clicking that it tells us to copy the sign-in link and then to open 1Password. This also didn't do anything for me; I'm guessing the client is supposed to notice the sign-in link in the copy-paste buffer and act accordingly, but nothing was happening (even after force-killing all remaining 1password processes and then opening it again). (Now that I'm writing this up I realize that I could probably have passed the link copied from the fallback page instead of grabbing it using the developer tools) 1Password Version: 8.10.30 Extension Version: 2.22.1 OS Version: Ubuntu 22.04.4 Browser: Chrome204Views0likes0Comments