Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration with KeePassXC keeps asking for ID #55

Open
Artim96 opened this issue Mar 21, 2022 · 5 comments
Open

Integration with KeePassXC keeps asking for ID #55

Artim96 opened this issue Mar 21, 2022 · 5 comments

Comments

@Artim96
Copy link

Artim96 commented Mar 21, 2022

I followed the instructions and created the file ~/.config/google-chrome/NativeMessagingHosts/org.keepasshelper.extension.json with the content

{
    "allowed_origins": [
        "chrome-extension://jgnfghanfbjmimbdmnjfofnbcgpkbegj/"
    ],
    "description": "KeePassHelper integration with native messaging support",
    "name": "org.keepasshelper.extension",
    "path": "/usr/bin/keepassxc-proxy",
    "type": "stdio"
}

and set it in the settings menu to Native Messaging. Browser integration is enabled in KeePassXC and the communication does work, but only up to the point of giving the communication key a name. Every time I enter a name for it and save it and then click on the extension icon again, it just asks again for a name for a new key. So KeePassHelper seems to request a new key every time. Why isn't it sticking?

@belaviyo
Copy link
Owner

What is your extension's version? Does the extension's interface keep open when the integration is happening?

@Artim96
Copy link
Author

Artim96 commented Apr 19, 2022

Extension version is 0.6.6.

The extensions interface stays open while setting the ID, but after confirming the ID, both the window of KeePassXC and the extension UI close.

@belaviyo
Copy link
Owner

Let's debug:

  1. Open chrome://extensions/ in a browser tab and turn the "Developer mode" on.
  2. Right-click on the toolbar button and select the "Inspect" item.
  3. On the new inspector window, switch to the "Console" tab.
  4. Follow the integration and see if you get an error in the console.

@Artim96
Copy link
Author

Artim96 commented Apr 19, 2022

ok...I don't know what changed, but it suddenly just works. Dev Mode has always been active. In the dev tools window there were no errors in console, but after setting the ID yet another time it suddenly worked. I did the exact same thing I did just this morning when writing the previous post - of course except the part with inspect popup.

So let's see if that's something permanent or if the problem reappears.

@Artim96
Copy link
Author

Artim96 commented May 25, 2022

I can confirm now that it "fixes" the problem reliably if when it keeps asking for an ID to simply use the "inspect" item on it. Then for some reason the popup seems to stay open for long enough to actually finish the connection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants