157

Ran into this issue today. It used to work, so something changed at some point, although I'm not sure when.

    17 days later

    The beta version of 1Password's Chrome and Firefox extensions (2.4.2 and 2.4.3 respectively) are working better for me than the current stable extension, but there's still some issues. Biometrics not working is one thing and depends on AgileBits whitelisting Orion, but the other issues (blank popup) and Chromium working fine (minus biometrics) make me think there's some extension API issues in Orion that might be worth another look by the team.

    Things I can do that I couldn't do in the stable version:

    • Log in to the extension (was hit or miss in stable)
    • Autofill suggestions show up below form fields
    • The extension popup menu shows up
    • Save passwords

    Issues:

    • Two-factor auth cannot be filled from the autofill suggestions, you need to copy it directly from the extension toolbar popup or from the app

    • Clicking the 1Password icon in a form field throws the "Collect Frame" promise warning noted below

    • If app integration is turned on in settings, there's a 5 second delay before the popup shows up

    • Sometimes the popup will just be blank, with no loading indicator, and the following warnings get logged to the console:

      Turning off app integration in the 1Password extension settings and restarting Orion reduces the delay and gets rid of the browser verification error (of course).

    • When the extension periodically locks (seems to ignore the 10 minutes setting), you'll need to enter your password. After unlocking the extension, I get a blank popup with no loading indicator regardless of the app integration setting. Going by the console log, it appears the extension unlocked successfully and loaded a page after 5 seconds, but the popup is blank.

    Console from the web inspector in the popup:

    When the blank popup after unlock issue happens, the only workaround is to restart Orion. Reloading or disabling/enabling the extension had no effect, the password field still appears to unlock the extension, followed by a blank page after unlock.

    From my testing, it appears Chromium itself isn't whitelisted by 1Password either, since biometrics don't work. Using the extension results in no errors and everything works as it should, which is why I think there's an extension API issue happening.

    11 days later

    I was getting somewhat excited when I read that @lkhrs got parts of the 1P extension working through the beta's.
    But I'm sorry to report that in my situation: subscribed 1P user within the EU (so using there EU 1P server) can still not stay logged into the service. I can enter my credentials but after switching websites and clicking the 1P icon in the toolbar to get to the 1P popup to fill a login I get kicked back to the following page while I just logged in.

    I tried it with both beta extensions, the one for Firefox and the one for Chrome. Both with same behaviour.
    I'm curious if and when the 1P team will come around. I'm following the Orion thread in their community but after messages from @Vlad and me and a few bumps nothing happened there.

    Maybe others can chime in with requests and comments:
    https://1password.community/discussion/124112/support-for-orion-browser/p7

      11 days later
      5 days later

      Ah that might be a clue (also a non-US server). But sadly I have no idea why?

        6 days later

        Currently getting by far the best experience with the Firefox Beta - Version 2.4.4.

        Even things like entering personal info and saving new Logins works.

        You can install it here: https://1password.com/de/browsers/beta/firefox/

        On some, but not most Websites you have to wait like 5 seconds after clicking Autofill.

        Also using the newest Orion Beta - Version 0.99.120

        P.S. Using US-Servers

          @Wupdich Thanks for your feedback. I tested it and with the EU server it still doesn't stay logged in.

          I contacted 1P support a while back. I explained that I was fed up with their lack of transparency. They answered the following:

          "Thanks again for your response. I don't have much insight into why we support Arc and not Orion. However, our developers are working on a feature that will allow 1Password to be added and used in every browser in the future. We just do not have a time frame on when that will be out, as these things are subject to change. I'm sorry I do not have more details to share."

          This still doesn't explain the selectiveness in supporting Arc and not Orion but if they solve the 'all browser' challenge then we're a bit closer to a solution.

          I currently turned off the automatic Log-out in the settings of the extension.

            I tried that as per your post but without any changes in behaviour. It still logs me out instantly.

              7 days later
              12 days later
              Merged 3 posts from Unable to use 1Password Extension.

                Unfortunately without a functional 1password extension I'm not going to be able to test Orion

                • Vlad replied to this.
                  3 months later
                  5 days later
                  a month later

                  Vlad It's true that version 8 doesn't require an extension to autofill, but there are a lot of things it can't do, which require the browser extension. These include:

                  • Generating passwords
                  • Saving login information
                  • Updating login information
                  • Filling personal information ("Identities")
                  • Filling Credit Card payment forms
                  • Privacy.com integration
                  • Fastmail integration

                  In addition of course to multi-platform operation, these are the kinds of features that people are paying for when they subscribe to 1Password, so people who are invested in 1Password are going to have a hard time giving this up to move to Orion. (Speaking for myself, I don't think even 30 minutes of Orion use go by without my noticing. It's just that I realize that it's in beta and issues like this are part of the deal.)

                    Yes, I agree with cob-nobbler those things I'm really missing from not being able to use the 1P extension in the browser. I would be grateful Vlad if you could reconsider making 1P fully opperational in Orion.

                      10 days later

                      Yep, the global autofill works, but is still missing a number of key features as cob-nobbled mentioned. I wo