keepassxc and bitwarden can not connected

[qw457812]

Issue: KeePassXC-Browser can not connected.

Fixed by:

mkdir -p ~/Library/Application\ Support/Glide\ Browser/NativeMessagingHosts
cp ~/Library/Application\ Support/Mozilla/NativeMessagingHosts/org.keepassxc.keepassxc_browser.json ~/Library/Application\ Support/Glide\ Browser/NativeMessagingHosts/

Ref:

glide/src/glide/docs/changelog.md

Lines 62 to 66 in 63001fb

	- Fixed the native messaging runtime path, previously the paths were the Firefox defaults now:
	- macOS system: `/Library/Application Support/Glide Browser`
	- macOS user: `~/Library/Application Support/Glide Browser`
	- Linux system: `/usr/lib64/glide-browser` (or `/usr/lib/glide-browser`)
	- Linux user: `path:~/.glide-browser`

Just want to document this in case anyone need it.

[qw457812]

I have migrated to Bitwarden. To fix the "Unlock with biometrics" option of Bitwarden Password Manager extension, do:

cp ~/Library/Application\ Support/Mozilla/NativeMessagingHosts/com.8bit.bitwarden.json ~/Library/Application\ Support/Glide\ Browser/NativeMessagingHosts/

Then re-enable the Bitwarden Password Manager extension.

[RobertCraigie]

out of curiosity why did you switch to bitwarden? I've been considering doing the inverse and moving to keepassxc

[qw457812]

Sorry for the delay. I'm a total KeePassXC noob and haven't read through all the docs.
So some of the pain points I'm about to mention might just be me using it wrong.

I was using KeePassXC on macOS and KeePassDX on Android, with Syncthing handling the sync between them.
I went with Syncthing because it seemed like the simplest option among KeePassXC's recommended sync methods.

Here is why I don't like KeePassXC:

1. Syncing via Syncthing is unreliable

   I was constantly worried that Syncthing might die in the background without me
   noticing - pretty sure this actually happened once on Android. This nagging fear
   about sync issues meant I never felt comfortable going all-in on KeePassXC.
   I couldn't bring myself to use strong random passwords for everything, so most
   of my accounts were still using the same weak password. With Bitwarden, I don't
   have to worry about the sync.

2. Bad workflow

   Creating new accounts with KeePassXC-Browser is not convenient. After generating a password,
   I have to actually click the register button before it prompts me to save credentials.
   Problem is, some sites do redirects that make this prompt disappear instantly, so I can't save anything.
   With the desktop app, I have to manually create a new entry after generating a password,
   then copy-paste everything - not automated at all.
   Bitwarden lets me save before even clicking register.

When GitHub recently started requiring 2FA, I figured it was a good excuse to give Bitwarden a shot.

After two or three days of low frequency use, I prefer Bitwarden.

I'm also curious why you want to switch to KeePassXC :)

Edit: I just found that KeePassXC-Browser can save username/password before clicking the register button,
but it requires a right-click and selection, see keepassxreboot/keepassxc-browser#1831 (comment)

Edit: Just found another reason to use Bitwarden - I can add Bitwarden extension to Android browsers like uazo/cromite, kiwibrowser, Edge Canary, and it can works.
I know that I can use the autofill of Bitwarden app on Android, this is a alternative.