Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
Trusted Browser Support - Windows
Good Day! Is there any word on when trusted browser support will be available for the Windows version? I am using Floorp as my browser (I wanted a Firefox/Gecko based browser that supports Workspaces...
Hello folks,
I'm happy to share that you can now add unsupported browsers as additional trusted browsers to 1Password for Windows. Follow these steps:
- Install 1Password in your browser from the appropriate web-store.
- Add the browser as an additional browser to 1Password: Connect additional browsers to the 1Password app
A couple of notes:- Make sure that your browser is installed system-wide with admin permissions in the C:\Program Files folder.
- When using an unsupported browser you might run into unexpected issues. If you see those same issues with a supported browser like Firefox or Chrome then let us know by starting a new discussion and we can investigate.
-Dave
+1 on this too. Since this feature for Mac was tested out over a year ago and the earliest Linux discussion was in 2021 this not being in Windows is a bit strange. At minimum, there has been over a year to think about this. Clearly its a priority for other platforms but not for Windows. Is there something technical that is stopping this, because from the logs all I can see is it is checking the signature of the exe against, probably, an internal allow list.2:INFO 2025-01-15T12:30:41.966+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:62] Verifying browser "C:\Program Files\Zen Twilight\zen.exe" for Zen and 2:INFO 2025-01-15T13:34:29.227+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:62] Verifying browser "C:\Program Files\Ablaze Floorp\floorp.exe" for Floorp.
1 │ INFO 2025-01-13T14:43:35.431+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src/main.rs:255] Starting 1Password-BrowserSupport 8.10.56 production build no. 81056028.
2 │ INFO 2025-01-13T14:43:35.460+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:62] Verifying browser "C:\Program Files\Zen Twilight\zen.exe"
3 │ ERROR 2025-01-13T14:43:35.467+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:71] WinApi(Error Win32(0x00002009): The directory service evaluated group memberships locally.)
4 │ INFO 2025-01-13T14:43:35.467+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:81] name: zen, publisher: Unknown Publisher, pid: 46376, version: 134.0.0.3
5 │ WARN 2025-01-13T14:43:35.474+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src\browser_verification\windows.rs:50] Failed to verify process parent. ParentVerificationFail(WinApi(Error HRESULT(0x800B0100): No signature was present in the subject.))
6 │ ERROR 2025-01-13T14:43:35.475+00:00 main(ThreadId(1)) [1P:native-messaging\op-browser-support\src/main.rs:288] Browser support error: ProcessVerification, happened in: native-messaging\op-browser-support\src\browser_verification\windows.rs:126
7 │ Additional error context: Process is not cmd.exe
Since I don't run chromium based browsers I would guess its the same for them. For those who want to find the logs its in AppData/Local/1Password/logs/BrowserSupport. Surely you can just have a toml file (since this is written in rust) that defines the exe's I am happy with not checking the signature of and just jump over the signature check since the 1Password extension and the app are already communicating
