1Password can't verify the identity of Chrome

cortig
cortig
Community Member
edited April 2023 in 1Password 3 – 7 for Mac

I'm using the 1Password Chrome extension and as of yesterday, I can no longer use 1Password in Chrome.
I systematically get a warning telling me that 1Password can't verify the identity of the web browser (on more than one Mac).

Everything is already up to date. I even tried redownloading Chrome from scratch, nothing doe it.

Corentin


1Password Version: 7.0 β 11
Extension Version: 4.7.1.4
OS Version: 10.13.4
Sync Type: Dropbox

Comments

  • @cortig,

    1Password checks the code signature of Chrome before it’ll connect. The most common reason for the code signature being wrong is that Chrome has downloaded an update but hasn’t yet been restarted. Please try running this command and post the output here:

    codesign -dv --verbose=4 /path/to/Chrome.app

    (replace /path/to with your path to Chrome)

    Ben

  • cortig
    cortig
    Community Member

    I don't see anything obviously wrong in the result:

    Identifier=com.google.Chrome
    Format=app bundle with Mach-O thin (x86_64)
    CodeDirectory v=20200 size=273 flags=0x800(restrict) hashes=3+3 location=embedded
    OSPlatform=36
    OSSDKVersion=658432
    OSVersionMin=657664
    Hash type=sha256 size=32
    CandidateCDHash sha1=a4633f8f8380178993601824f4fdfc68a4c39009
    CandidateCDHash sha256=6a63595b84552f99e80e032b4ca0a73fb4f645ea
    Hash choices=sha1,sha256
    Page size=4096
    CDHash=6a63595b84552f99e80e032b4ca0a73fb4f645ea
    Signature size=8949
    Authority=Developer ID Application: Google, Inc. (EQHXZ8M8AV)
    Authority=Developer ID Certification Authority
    Authority=Apple Root CA
    Timestamp=May 7, 2018 at 15:52:31
    Info.plist entries=36
    TeamIdentifier=EQHXZ8M8AV
    Sealed Resources version=2 rules=7 files=182
    Internal requirements count=1 size=240
    

    Corentin

  • cortig
    cortig
    Community Member

    And @ben, the app is already up to date. To triple-make-sure, as I was saying, I redownloaded the app and reinstalled it to ensure I had the latest version and it would not have any update running in the background.

    Corentin

  • @cortig,

    Thanks. Hopefully the report I requested in your other thread will be able to get us pointed in the right direction.

    Ben

  • cortig
    cortig
    Community Member

    I posted a reply in the other thread: apparently β 11 doesn't support browsers that are not located directly in /Applications.

    Corentin

  • Replied in the other thread. Since this all comes down to the issue discussed there I’m going to close this thread and we can continue the conversation over there. :)

    Ben

This discussion has been closed.