-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Browser integration: KeePassXC icon/auto-populate appears in all fields in webapp (Synology) #2404
Comments
Is there a demo page or a public instance where this can be tried? There's two more open issues where Synology is mentioned. |
I have a synology NAS and didn't notice any errant KeePassXC icons anywhere in the dialogs. I think I have a different software than the OP though. |
You can create a demo environment via https://demo.synology.com |
What is the exact portion of the admin console that shows this problem? Your screenshot was not specific and I don't understand the language. |
Overview
Hello,
I'm using KeepassXC browser integration to log into the web interface of my Synology NAS.
Once logged, KeepassXC icons will appear on all kinds of fields and propose to populate the field, even if it's not a login/password field.
Steps to Reproduce
Expected Behavior
Only propose auth information at login page and / or on login/password fields
Actual Behavior
The auth information are pushed to all fields
Context
This mostly applies within a specific web application (admin portal of Synology NAS)
In the following screenshot:
KeepassXC browser integration tries to populate the first field (the field is for an IP address)
The icon appears in the "repertoire" field and auto-populates it with a login (the field is for a text entry, a directory)
KeePassXC - Version 2.7.9
Révision : 8f6dd13
KeePassXC - Version 2.7.9
Révision : 8f6dd13
Qt 5.15.11
Le mode débogage est désactivé.
OS : Windows 11 Version 2009
Architecture : x86_64
Kernel : winnt 10.0.22631
Extensions activées :
Bibliothèques cryptographiques :
The text was updated successfully, but these errors were encountered: