Safari Extension won't fill if too many tabs open
Folks, I am having an intermittent problem where the 1Password extension will not autofill. You clink the icon in the web page, nothing happens - no pull-down menu If I use the icon at the top of the browser, it can recognize the site, but when I click autofill, it won't work. 1Password and safari are both updated Solutions I've found - quit and restart Safari - very inconvenient Open a new safari window - much less disruptive but still annoying This sounds very similar to the problem reported ~3 years ago at: Autofill stops working on Safari tab | 1Password Community, but that user was using beta Safari version,, Thanks in advance for any advice and hopefully a solution!25Views0likes2CommentsGenerating Passkey on Second Account
My wife and I have a 1Password family plan and we both have separate logins into our joint account at Capital One. I created a Passkey for my login at Capital One. When she tries to login, a dialog box appears saying "Sign in with a passkey" that is linked to my account. When I close that box, another dialog box appears asking how I would like to sign in: iPhone photo of a QR code or via a Security Key (which I interpreted optional ways to open my account). When I cancel that option, then I can click on the "Sign in using a Passkey" button (which is how I generated my passkey), but when I do that the first dialog box reappears offering to sign in with my passkey. I can sign in using her user name and password, but once in the account, I don't see a option to generate a passkey. As I mentioned, when I generated my passkey, I clicked on the "Sign in using a Passkey" button to generate the passkey. How do I generate her passkey? Thank you.33Views0likes1CommentAWS Shell plugin is not providing session token
Hello, I tried to set up AWS shell plugin in a way that it'll provide me short lived tokens. I need these for our internal tools that use AWS SDK and is able to work with these temporary credentials, so 1Password doesn't see this to be something originating from `aws` cli. I'm trying to understand how can I use 1Password to only hand out temporary credentials so that the application doesn't have to deal with getting the tokens itself. According to Shell plugin docs (https://developer.1password.com/docs/cli/shell-plugins/aws/#optional-set-up-multi-factor-authentication) there should be session token set up, but I don't see it. I don't understand how it should get there and when should it be available. It's currently set up in this manner and aws plugin seems to be able to use MFA: op % op item get xyz ID: xyz Title: AWS Vault: Employee (abc) Created: 2 years ago Updated: 20 minutes ago by [me] Favorite: false Tags: XXX Version: 42 Category: LOGIN Fields: username: [username] password: [use 'op item get xyz --reveal' to reveal] access key id: [access-key] secret access key: [use 'op item get xyz --reveal' to reveal] one-time password: 123456 mfa serial: arn:aws:iam::[rest] Default region: [region] Account ID: [account-id] URLs: website: https://us-east-1.console.aws.amazon.com/iam/...25Views0likes2CommentsNew sign-in alert
About an hour ago, I received an email saying that there had been a sign in to my 1Password account from a new device (Safari extension). From the message, I couldn't tell on what hardware this took place, so I followed the guidance, logged in to my account, and reviewed the devices linked to it. Although the recent ones looked familiar (the device names, IP addresses, and locations were correct), the OS information was wrong. For example, the iPhone showed iOS 17.4, whereas I'm running 26.1. The version of macOS was also incorrect. To be safe, I unlinked all the recent devices and reset my account by generating a new Secret Key and password. I was able to log in on my two main devices using this information plus MFA (see below). I'm in the Manage account page on my Mac and can see it as Your current device, but the macOS version is still wrong. I have three related questions: The incorrect versions of macOS and iOS threw me and perhaps led me to reset my account unnecessarily. If this information isn't reliable, why is it shown? As above, I wasn't able to tell what hardware had been used to sign in to my account in the first email notice. What is the best way to do this? I have MFA set up using the Authenticator app on my iPhone, and it was active at the time I got the notice. If so, does this mean that an unauthorized user couldn't have signed in to my account, and am I good to go? Thanks!7Views0likes0Comments"Connection Refused" when accessing 1Password ssh-agent within DevContainer
I've been trying to get this to work for a few hours and I'm at a loss for what to do next, so asking for ideas about what the problem could be. My software stack is macOS 26/Tahoe, 1Password 8.11.16, Orbstack (for containers), and VSCode w/DevContainers. I have my SSH keys in 1Password and when executed from the host system, the keys are visible (and SSH works): % SSH_AUTH_SOCK="${HOME}/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock" ssh-add -l 256 SHA256:... (ED25519) % ssh -T git@github.com Hi <username>! You've successfully authenticated, but GitHub does not provide shell access. I have the DevContainer configuration to bind-mount the socket into the container and set a proper `SSH_AUTH_SOCK` value: "mounts": [ "source=${env:HOME}/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock,target=/tmp/ssh-agent-1password.sock,type=bind" ], "remoteEnv": { "SSH_AUTH_SOCK": "/tmp/ssh-agent-1password.sock" }, ... when I am in the container, the socket looks right, `SSH_AUTH_SOCK` is correct, but `ssh-add` fails to connect with an error: root@5a53d7e1c685:/tmp# ls -la ssh-agent-1password.sock srw------- 1 root root 0 Nov 2 16:36 ssh-agent-1password.sock root@5a53d7e1c685:/tmp# echo $SSH_AUTH_SOCK /tmp/ssh-agent-1password.sock root@5a53d7e1c685:/tmp# ssh-add -l Error connecting to agent: Connection refused I've verified that the directory itself IS accessible to docker by changing `source=${env:HOME}/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock` to be `source=${env:HOME}/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sockk` and restarting the container -- when I do that, the directory `agent.sockk` is created within the directory as expected (which I am interpreting as evidence that Docker can traverse all the way to the directory and create a sub-folder within it). I suspect what is happening is that 1Password is blocking the connection entirely (meaning it isn't a filesystem permissions error or otherwise), but I'm not sure how to prove that is the case or how to fix it if it IS the case. Any ideas for diagnostic steps to take next?Solved42Views0likes2CommentsChrome plugin popup doesn't close anymore
On Chrome for Mac I have installed the 1Password plugin. Since recently, the popup that opens up prompting to save credentials won't close anymore no matter what I do - clicking on the 'x', clicking outside, pressing on the 'Unlock 1Password' button, hitting the Esc key. Chrome version: 141.0.7390.123 (Official Build) (arm64)14Views0likes1CommentNew in Beta: App Unlock Presets + Unlock with Device for Mac
Hey everyone. Weβve got two exciting new features ready for you to preview in 1Password for Mac (Beta release channel). π π App Unlock Presets A new Security Review section in the sidebar lets you quickly review and update how and when 1Password locks on your Mac. Choose from a selection of optimized presets: Convenient, Balanced, or Strict, or fine-tune settings to match how you actually use your device. π₯οΈ Unlock with Device When enabled, 1Password will lock when your Mac locks, and unlock when you unlock your Mac. (No extra prompts!) It uses built-in macOS platform security to make your workflow smoother and keep your data safe. "Unlock with device" is enabled by default in two of the new presets. You can switch presets or adjust individual settings anytime in Settings > Security. Whatβs next? Our goal is to make 1Password work the way you do: less fiddling with settings, fewer interruptions to your workflows, and the same high level of security you expect. So we're going to roll out the new unlock experience to everyone over the course of the summer. β Windows, Android, iOS, and web β Support for Team and Business accounts β Extensive admin controls for team-wide auto-lock settings π Weβd love your feedback, especially on Unlock with Device! To try out the Mac beta: choose Settings > Advanced > Release channel > Beta, and then choose About > Check for Updates. These features are currently only available in Beta for Individual + Family accounts on Mac (not Business accounts β yet!)1.1KViews4likes17Comments