Support for Orion Browser

I'm using a brand new, completely clean install of Orion RC and was able to connect 1Password successfully with the extension.

The dropdown on the input field with my logins is pretty hit or miss whether it will show up. It's honesty about 50/50 (It doesn't work on this site, for example). When it does, it responds to hover events, but clicking on a login won't auto-fill. Looking at the console for the extension, I do see a console error (this is the console specifically for the extension and not for the site I'm auto-filling):

I can open the mini-window from the extension but clicking "Autofill" provides a console error as well:

Maybe about a third of the time, the mini-window won't load when I click the extension button. I usually have to restart the browser to get it working again.

Great to see support for Orion in 1PW. I tried it and it worked (although sometimes the addon still blanks out and refuses to load).

However, Passkeys seem to be completely non functional. When signing in to a website with a saved passkey inside 1PW, Orion just shows the „insert USB passkey device“ prompt and ignores the saved one inside 1PW. This works fine in chrome.

Is this something that’s actively being worked on?

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.

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.

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.

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.

1P_Mitch I'm not sure what the difference is in terms of practical use?

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.

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.

Unsure if this is an Orion or 1P issue.

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