Edge Chromium Extension



  • MikeTMikeT Agile Samurai

    Team Member

    On behalf of the team, you're welcome.

  • edited August 22

    **UPDATE: ** Nevermind. It's early. I need more coffee. All is working.

    I have 1Password for Windows (Current Edition, Beta enabled) and 1Password for Edge and Chrome enabled. I can't seem to figure out how to get the extension loaded into the Edge Chromium dev instance. Is it because I'm running the Canary build?

  • bundtkatebundtkate

    Team Member

    I'm fairly convinced I always need more coffee, @rwsmith_scf. Or I just want an excuse to drink more coffee. Either way, I hope you've now got a cup on your desk and I'm glad all is well. Enjoy the new Edge and if we can do anything more to help, you know where to find us. :chuffed:

  • @bundtkate I am enjoying the new Edge Chromium, and also more coffee, but it all can't help with me being eager to get 1P 7.4 for Windows. ;)

  • brentybrenty

    Team Member

    Ha! We're eager for you to have it too, but only when it's ready. :)

  • tryphoontryphoon Junior Member

    What about Edge Chromium on Mac OS X?

  • brentybrenty

    Team Member

    It's a possibility. This discussion is about Windows though. :)

  • Hi,

    Just a warning that upgrading to Edge Dev that just came out (10 September) makes the latest 1P app 7.3.712 beta fail. It was working ok just prior to the Edge update.

    When Edge Dev is launched it complains that! with the warning:

    (https://us.v-cdn.net/5020219/uploads/editor/zm/84m60ou7so3z.png "")

    The 1P extension button is blanked out and opens up a generic menu.

    The logs contain the following:

    Refusing helper connection from "C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge.exe", because of untrusted certificate.

    I've just sent a set of diagnostics for another thread about the .712 upgrade problems.

  • bundtkatebundtkate

    Team Member
    edited September 10

    It looks like ChromiEdge changed its code signature with that update, @wigster. I see the same issue myself after forcing an update just now. I have flagged this for our development team so that they're aware and can take a closer look. :+1:

    Thanks for letting us know, too! I have so many browsers installed for testing, but I definitely don't use all of them often enough to notice these troubles right away so the heads up is much appreciated. :chuffed:

  • Browser connection refused :(....
    Version (Official build) dev (64-bit)

  • @scottyjn can you check who signed your msedge.exe file and share with us?

  • Hey Sergey...I just received another update for Edge a minute or so ago.
    Version (Official build) dev (64-bit)
    The issue is now resolved :)

  • MikeTMikeT Agile Samurai

    Team Member

    Great, thanks for the quick update.

  • KeiferKeifer
    edited September 29

    Maybe I'm just slow, but I had significant difficulty trying to figure out how to get either the Chrome extension or the 1Password X browser app working on the Microsoft Edge Chromium Beta (version 77 or 78). So I figured I'd give people a step-by-step. Hopefully this helps someone :)

    1. Click on the ellipses
    2. Click Extensions
    3. Click Allow extensions from other stores
    4. Go to the Chrome Extensions Store and search for 1Password - https://chrome.google.com/webstore/search/1password x
    5. Click Add to Chrome on any of the options that come up. I personally chose the 1Password X (non-beta) version and it worked great
  • brentybrenty

    Team Member

    Glad you're enjoying the beta! I find it's simpler to just go to https://1password.com/downloads/#browsers since that's "one-stop shopping" for everything 1Password. And once Edge is finished and there's an official way for us to offer 1Password for it, I am sure we will have a download link specifically for that as well. Cheers! :)

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file