Please add support for the https://browser.kagi.com. It needs explicit signature verification from 1Password to work. Otherwise, it should work out of the box.
1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided
Hey everyone! I have some good news to share right before the holidays.
Orion and 1Password
I can confirm that Orion 0.99.126.4 works very well out of the box with the 1Password extension for Chrome. Highlights include:
A fix for a condition where 1Password autofill suggestions would either not appear at all, or would not respond properly to user input
Passkey support 🥳
Thank you to Vladimir and the Orion team for these updates.
The setting to connect 1Password for Mac to any web browser that you trust has graduated from Labs, and shipped to the stable channel this week in 1Password 8.10.22. This setting allows you to unlock the browser extension using Touch ID and use other features which depend on a connection between the browser extension and the desktop app.
You can add Orion to the list in Settings > Browser > Connect to additional browsers.
With the new setting in 1Password, and the more comprehensive support for Chrome extensions in Orion, it should now be possible to have a very successful experience.
Getting help and support
While we support everyone's choice to use 1Password with any web browser, please be aware that for practical purposes, we have a limited ability to help with specific browsers outside of the ones that we actively test. You can help us help you by following these guidelines:
If you experience an issue with 1Password in Orion, please try to confirm it in one of our officially supported browsers. Reproducing the issue in, e.g. Chrome, will make it clearer that the bug is on our end and will also make it much easier to troubleshoot and address.
If you believe the issue is related to the setting in the desktop app (e.g. the extension is otherwise working, but does not unlock automatically when you unlock the Mac app) then please let us know on this forum.
If the issue does not seem related to the desktop app integration and cannot be reproduced in another web browser, it may be best to report it on the Orion public issue tracker: https://orionfeedback.org/. The Orion team is working to ensure full compatibility with Chrome extensions but this is an ongoing process.
@1P_Ben Yes. I do have that turned on and have the same "Connected" with the green circle/ball as shown in your image.
BUT ... i hadn't yet updated to 0.99.124.4.5-rc ... doing that now.
Nope ... no change in behavior (both CMD-\ and the regular browser drop down that shows up in username / password fields and working [or not working] as described in my post above).
A
Anonymous
Jul 12, 2023 4:13 PM UTC
working for me on Orion RC and the new 1P nightly! took far, far longer than is reasonable but glad it’s here at last
I also tried to get it working with Thorium out of curiosity (which is a very minimally-modified build of open-source Chromium) but am unable to add it to the trusted browsers list—when I select the app, no consent modal appears and nothing gets added. I don’t use Thorium actively anymore so not a huge deal for me but figured I’d report this anyways since the 1P has mentioned that the trusted browsers feature is intended to work with other Chromium browsers out of the box
I can confirm some of @scottharris1014 behavior. Namely the shortcut key to open the auto fill box not detecting the page I am on. Also some hit-or-miss behavior depending on the page.
Thanks for trying it out and sharing your feedback, everyone!
@scottharris1014: Thank you for the bug reports. Support for trusted browsers has focused on compatibility with the browser extension, so it doesn't yet extend to the autofill capabilities that originate from the desktop app (Quick Access/Command-\). We're looking into what we can do here.
As for issues with the extension autofill: does it work as expected in other browsers with the same sites and logins?
@tiltowaitt: you can use the 1Password browser extension in Orion by itself without connecting to the Mac app, but linking the two will require 1Password 8.
A
Anonymous
Jul 12, 2023 4:26 PM UTC
@1P_Mitch I'm not sure what the difference is in terms of practical use?
A
Anonymous
Jul 12, 2023 4:43 PM UTC
@1P_Mitch
Thanks for the info (I'd thought from the name "Trusted Browser" and the fact that CMD-\ works just fine with regular Orion that adding Orion RC as a trusted browser would put it on par with regular Orion and get rid of the "can't verify" popup).
I did check using the extension on Chrome with the Washington Post website and with another one (PacerPro) that didn't work right with Orion RC -- both work as expected with the extension in Chrome: I choose my login from the drop down, it fills in the user name then autofills the password field without further input from me.
A
Anonymous
Jul 12, 2023 6:35 PM UTC
Want to flag a fresh issue I'm having on my second Mac that might be related to some of the issues others are experiencing in this thread. For some reason 1P is refusing to switch to the nightly channel on this Mac.
I previously was on the Beta channel. After switching to Nightly, it still just shows "You're up to date!" and "on BETA channel" in the About page.
I've tried:
Uninstalling and reinstalling 1P
Using the "Reset 1Password" button on the Advanced page
Uninstalling 1P, deleting the Group Containers folder (per https://support.1password.com/cs/starting-over/), and reinstalling
Uninstalling 1P through CleanMyMac to delete all related files/folders completely and reinstalling
After fully resetting the 1P app, even if I install the Production 1P version and select Nightly, it forces me into the Beta channel despite a complete wipe of 1P and never having selected Beta.
It seems like there could be some server-side flag that's forcing my device to be stuck on the beta channel instead of nightly? Happy to share diagnostics files if helpful.
Hey there @Sankcool, thanks for trying things out,
Regarding your attempted use of Thorium, my suspicion after reading your message was that it doesn't have a code signature. I checked it out myself locally and confirmed this: The developer is only distributing the build with an ad-hoc code signature, and not a "proper" development certificate/key issued by Apple. You can see this either running codesign -dvvv on the app bundle locally, or using WhatsYourSign:
Per @1P_Mitch's earlier post about the feature, only browsers signed by a valid Apple development certificate are supported for the time being, sorry. We're trying to gauge if this is something that could be improved upon, but I don't have much else to share at this time.
We will definitely work on improving the error feedback there though to make things more clear.
Regarding your updater troubles, these should be resolved as of tomorrow morning (if not a bit sooner). We are tracking an issue where the release of a beta with a newer version prevents nighties from being seen. Sorry for the trouble here.
Thanks for giving the feature a try, and we appreciate the feedback.
A
Anonymous
Jul 14, 2023 3:32 AM UTC
Thanks for looking into things @ag_Christian, that all makes sense and will try updating on the nightly channel again. I'd personally vote for the code-sign requirement to be loosened (maybe showing a danger alert when an app is self-signed but still allowing the user to override?) given that many open-source Chromium builds aren't codesigned with Apple developer program certs—but totally understand if that's a bit too far for 1P's comfort with regards to security given the scope of access being granted here. Will note that the 1P extension otherwise works as expected so it's not a huge loss either way, just need to login to each vault manually and type in the master password more frequently.