-
Notifications
You must be signed in to change notification settings - Fork 38
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
Provide an additional data item for an entry to do a more specific query selector for input #52
Comments
Thanks for your suggestion - can you provide a couple of examples where VaultPass currently does not work correctly? |
Sorry, meant to reply sooner. Here's one example, which is from VMware's vrealize product. It actually automatically sets the authentication type dropdown as the username and leaves the username blank.
It looks like the following when vaultPass is not filling the fields. I'll try to update with more as I encounter them, I only hit some of these systems every few weeks or longer. Note: I'm not against doing this myself and providing a PR if I end up with time, I submitted an issue so it was tracked in some way and in the (unfortunately likely) case that I don't get time and get around to it, it's not entirely lost. |
Thanks for replying anyways! I don't have access to vRealize right now... but I could check it out for my vCenter lab... maybe the login is the same style? |
On some sites, vaultPass does not correctly find the username and/or password inputs to add the saved data to.
Provide inputSelector.username and inputSelector.password (or equivalent) vault data items that if present are used (and preferably prioritized) as additional query selectors in the findPasswordInput() and findUsernameNodeIn() functions in content.js. This likely means sending it as an additional item through the fill_creds message sent inthe extension.
Other than continuously adding additional selectors that are attempted for the username, I'm not sure of how to handle sites automatically that don't meet current expectations for what forms a username input can take. Manual copy and paste works, so this isn't a change required to fix the plugin from being non-functional, but it would be a nice quality of life improvement.
Whether to allow this for the password entry is slightly more complex of a problem, as allowing the password to automatically be entered into a non-password type input and have it visible may be a security regression not worth doing. Even so, I think the username field is in my experience the one more likely to need this help, so not supporting the password input in this way doesn't negate the usefulness of this suggestion entirely.
The text was updated successfully, but these errors were encountered: