Keepassxc-browser: Autofill no longer works after last update

Created on 12 Oct 2018  路  4Comments  路  Source: keepassxreboot/keepassxc-browser

A few days ago, KeepassXC-browser self-updated in Firefox. Then it requested that I update KeepassXC because it was out of date.

After updating KeepassXC, autofill no longer works.

Context

Entry in KeepassXC:

username: gwerbin
password: ball123
url: github.com

Navigate to https://github.com and make sure I am logged out.

Expected Behavior

I am prompted to autofill the username and password. Occasionally the plugin "misses" and I need to press "redetect credential fields", but otherwise things "just work".

Current Behavior

No autofill at all.

Possible Solution

No idea.

Steps to Reproduce (for bugs)

Honestly not sure. Be me, I guess.

Debug info

KeePassXC-Browser Version: 1.3.0
KeePassXC Version: 2.3.4
Windows 7 Enterprise SP1
Firefox 62.0.3

No error in KeepassXC, nothing in browser JS console.

Most helpful comment

I see. Whatever the behavior is, a note somewhere on the website about URL/domain matching behavior would be appreciated (and help make KeepassXC more accessible to non-technical users)

All 4 comments

Change your entry URL to https://github.com.

@varjolintu that fixed it. Is this new behavior? Or perhaps a spacebar heating bugfix?

Will https://example.com work on subdomains like www or will I need a separate reference entry for those? And will it no longer work on plain http (which is a good thing)?

Going to be kind of a pain to modify all my URLs. Maybe I'll make a backup and write a script to work on the XML...

Edit: is this behavior documented anywhere? I couldn't find it on the KeepassXC site.

The URL matching was broken and fixed with 2.3.4 but one bug remains, and that's the subdomain matching. See https://github.com/keepassxreboot/keepassxc/pull/2253. If your entry's scheme is http it will no longer work with https. When the subdomain fix is merged, then http://example.com with match with https://*.example.com etc.

So for now, there is no workaround for it. You'll have to wait for the next release, or use a snapshot release when the fix is merged.

I see. Whatever the behavior is, a note somewhere on the website about URL/domain matching behavior would be appreciated (and help make KeepassXC more accessible to non-technical users)

Was this page helpful?
0 / 5 - 0 ratings