Trusted Browser Support - Windows

Why is this marked as having a solution?  "The team hopes to build a secure way to use unsupported browsers" is in no way a solution.  There are very few browsers that still support manifest v2, like Floorp.  So how about you get your priorities in the correct order and get this fixed?  Other than fixing a Zero-day exploits, this should be your top priority.

Hi. I would like for this to be implemented too. Windows needs it. Arc, Zen, Floorp are just a few.

Whats the priority of this? It is still being working on? 

I ask because the last beta update for windows has 4 "cosmetic" bugs and 1 functionality. I'm not saying that these are not important, but it feels that this feature request got discarded.

I love 1Password, there is not a single competitor that has all of its functions, I really want that they continue improving and bring this requested feature to their clients.

I saw this was kicked down the road again 3 months ago, and this after 2 years of "we're working on it," which makes me think the 1Password team has no intention of ever releasing this. I would prefer an honest answer, whether it be "There's a technical issue with XYZ that creates a potential security breach we are not comfortable with allowing" or "We don't know when or if this feature will be worked on as we have other priorities we want to focus on" or something else. This constant kicking it down the road nonsense is insulting, and nobody is buying it. The fact there's a solution for both Mac and Linux and, according to Wavebox's documentation, there USED to be an option for this in the Beta release of Windows (https://wavebox.io/kb/1password-extension/) is frustrating, to say the least. The Trusted Browser support allows other developers, in my case, Wavebox, to integrate tightly with the Desktop version, allowing Windows Hello unlocking just like in "standard" browsers such as Chrome.

Can we get a REAL update from the 1Password team on either of these?
A) There's a technical or security issue we don't forsee being able to overcome therefore this is on an indefinite hold
B) We have many other features we want to work on first and therefore we have no idea if or when we'll get to this feature request.

Another 4 months have passed, and still nothing. No sign of the extra Browser options for Windows... We are waiting for years now, and all you can keep saying is "we are working on it" or "I will pass your concerns to the team".

Why can you not just give a feature like this some priority and have it released in 1-2 months. Many people want this, because this is not the only topic about this issue.

Mind-blowing that this issue is open for 2 years and the developers still don't have any ETA on when this feature will be implemented. I expect a lot more transparency from developers as a paying customer. It's very annoying to open the extension and enter my password every ten minutes to the point that I'm considering using alternative products.

So you're not able to properly support more than a small selection of browsers for the most used desktop OS in the world, when you're making software with the main purpose of filling passwords (typically done on a desktop OS).

I really hope this is your top priority at the moment, 1P_Dave? Because I will be looking to alternatives if this isn't fixed by summer.

I enjoy coming back to this thread occasionally and checking the status. I'm dismayed that this feature still isn't implemented, but I'm encouraged by how many people have commented.

I'm hoping to see this implemented soon. 1password is a beast, so I'd really like to have this one feature implemented to eliminate this frustrating situation.

Thank you, 1P_Dave - hope it's appropriate to mention you there and indicate I am looking for this feature. Additional info in case it's useful for your tickets, teams, etc. (I understand it may not be):

• This is an accessibility feature for me. I have cognitive disabilities that mean a break in my "flow" every time I need to "connect" the login will be disruptive. (I also want to say that, in contrast, when the "unlock with desktop app" functionality was first introduced, it was extremely exciting and helpful, so: good job!)

• The lack of ability to trust additional browsers has, because of the previous concern, stopped my migration from one browser (Edge or Arc) to another (Floorp) twice in the past six months or so. Floorp is still my current browser of choice, if not for the missing "trust' link.

Thank you!

+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