Unlocking Desktop, doesn't unlock browser extention

I'm experiencing the same issue on Chromium, but it's as-if the extension is an entirely disconnected and separate app:

• Re-installing it and clicking it makes it want to 'sign in' to connect to my 1Password account.
• With the extension signed in and the desktop app unlocked, clicking the extension does not make it auto-unlock (even after waiting).
• With the extension signed in and the desktop app locked, clicking the extension does not make it auto-lock (even after waiting).

Honestly, the new extension gives me 1Password X-like PTSD symptoms, and almost makes me regret having a 20+ character password.

While I might be exaggerating a bit here, both of these apps (1Password X and the new beta extension) feel like they obstruct the goal I'm trying to accomplish instead of supporting me in leading a secure digital life, but I suppose that's feedback for a different team altogether.

EDIT: Could it be that the extension is failing to communicate in Chromium for a similar reason that the 1Password 7 extension failed in Chromium, because it was looking for / expecting a (hardcoded) path to Chrome's installation? I remember that with that version of the extension, 'creating' the path even if Chrome itself wasn't installed would magically make it work in Chromium as well.

EDIT 2: Found the 'path' workaround mentioned in my previous edit ( mkdir -p ~/Library/Application\ Support/Google/Chrome ), but even with that the problem still persists.

@claudiodekker As far as I see 1Password does not list Chromium as a supported browser.

Hi @claudiodekker:

The short version is Chromium is not a codesigned web browser, and according to the developers it never will be. The end result of that is that because of it's lack of codesigning, 1Password for Mac will not talk to 1Password in your browser. Because of that, while you can manually unlock and lock 1Password in your browser as you mentioned, it will not share a lock state with 1Password for Mac.

Jack

Hey @"jack.platten",

I understand that Chromium isn't code signed, but I'm still curious whether there's a way to 'disable' this security/integrity somehow, as previous extensions worked just fine when DIY'ing a workaround. It doesn't even need to be a toggle in the app, even an app-level or configuration file patch that I'd have to (re)apply manually every time the app updates would more than satisfy me.

Of course, I understand that there is a technical argument to be made with regards to near-guaranteeing the safety of the extensions by only talking to code-signed browsers, but to the (highly technical) users that go out of their way to (constantly) compile and run up-to-date Chromium builds, this feels like more of a limitation. At least speaking for myself, I don't run Chromium because I enjoy compiling my own browser for hours every week, but rather because even though Google's track record with privacy and the protection of user data is arguably poor at best, they still make the most web-compatible browser out there these days.

Thanks