When using the global password only autotype, I think it is reasonable to expect AutoTypeSearch to only autotype the password, however at the moment this shortcut is treated exactly the same way as the default global autotype.
This is important for me because due to so many sites using two-step login (or whatever its name may be) like Google and login forms being different and somewhat unpredictable, I've decided to make my global autotype only autotype the username. This allows me to completely control what gets written and where it gets written by first using the default global autotype, then the password only one when and where it needs to go.
I don't know if the two can be distinguished at this plugin's level, but I really hope so.
Have a nice day and merry Christmas! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, if I've understood you correctly, then the desired behaviour is that if you have the AutoTypeSearch option to "Show automatically if global auto-type finds no match" is turned on, and if you use the KeePass Global Auto-Type keyboard shortcut. If that fails to find a match AutoTypeSearch will be shown. If you then search select an entry, you would expect it to auto-type the password only.
That seems reasonable to me. I will investigate and see if is possible to integrate in this way - I suspect by the time it gets to AutoTypeSearch the information has been lost about which hotkey KeePass is responding to.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sadly it seems my suspicions were correct. There is no way for a plugin to determine which hotkey caused an unsuccessful autotype. I can't find any way to obtain that information from KeePass.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Damn it! Do you think there could be a way to circumvent this? Like what if we could trick KeePass into thinking it was successful? (This assumes that would make any difference, which I have no idea of course.)
Or would it be possible to catch another plugin's shortcut maybe? Like AlternateAutoType's (https://sourceforge.net/projects/alternateautotype/)? I guess that would require work from both plugins to allow interoperability which might not be something you guys would want to do, which I would understand.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could try using CheckPasswordBox - that can be used to alter the auto-type behaviour to type only the password if the focus is in a password-box. As it takes effect during the auto-type itself, it shouldn't matter if the auto-type comes from an AutoTypeSearch result or from a hotkey.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would it be possible to add "AutoType Password only" as an alternative action to auto-type? This way if the user wants to only type password, configure Alternative Action (Shift+Enter) to auto type password only. While not as nice as detecting which hot key was used, this may be good enough.
I know that there already is an Alternative Action to copy password (to clipboard) but I think auto type password is better.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't think that works with autotypesearch plugin.
Use case:
1. Press hot key for auto type password only (Ctrl+Alt+Shift+Enter)
2. No entry found and auto type search dialog automatically displayed
3. User enter the search entry and select one of the entries found (either with Enter or with Shift+Enter)
4. Auto type search plugin either executes the normal auto type (i.e. username and password) or what ever is configured as alternative action (including copy password to clipboard but no option available to auto type password)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oops. I didn't notice that you posted in the auto-type search forum.
The password only option is the last option in the either the normal or alternative action dropdown menus. See the attached screenshot showing the option selected in the alternative action.
Hi,
When using the global password only autotype, I think it is reasonable to expect AutoTypeSearch to only autotype the password, however at the moment this shortcut is treated exactly the same way as the default global autotype.
This is important for me because due to so many sites using two-step login (or whatever its name may be) like Google and login forms being different and somewhat unpredictable, I've decided to make my global autotype only autotype the username. This allows me to completely control what gets written and where it gets written by first using the default global autotype, then the password only one when and where it needs to go.
I don't know if the two can be distinguished at this plugin's level, but I really hope so.
Have a nice day and merry Christmas! :)
Hi, if I've understood you correctly, then the desired behaviour is that if you have the AutoTypeSearch option to "Show automatically if global auto-type finds no match" is turned on, and if you use the KeePass Global Auto-Type keyboard shortcut. If that fails to find a match AutoTypeSearch will be shown. If you then search select an entry, you would expect it to auto-type the password only.
That seems reasonable to me. I will investigate and see if is possible to integrate in this way - I suspect by the time it gets to AutoTypeSearch the information has been lost about which hotkey KeePass is responding to.
Sadly it seems my suspicions were correct. There is no way for a plugin to determine which hotkey caused an unsuccessful autotype. I can't find any way to obtain that information from KeePass.
Damn it! Do you think there could be a way to circumvent this? Like what if we could trick KeePass into thinking it was successful? (This assumes that would make any difference, which I have no idea of course.)
Or would it be possible to catch another plugin's shortcut maybe? Like AlternateAutoType's (https://sourceforge.net/projects/alternateautotype/)? I guess that would require work from both plugins to allow interoperability which might not be something you guys would want to do, which I would understand.
You could try using CheckPasswordBox - that can be used to alter the auto-type behaviour to type only the password if the focus is in a password-box. As it takes effect during the auto-type itself, it shouldn't matter if the auto-type comes from an AutoTypeSearch result or from a hotkey.
Would it be possible to add "AutoType Password only" as an alternative action to auto-type? This way if the user wants to only type password, configure Alternative Action (Shift+Enter) to auto type password only. While not as nice as detecting which hot key was used, this may be good enough.
I know that there already is an Alternative Action to copy password (to clipboard) but I think auto type password is better.
Actually just noticed that on the sourceforge page, it says "Auto-typing the password only is also supported."
How is it supported?
See the System-wide hotkeys section in menu
Tools>Options>Integration(tab)Don't think that works with autotypesearch plugin.
Use case:
1. Press hot key for auto type password only (Ctrl+Alt+Shift+Enter)
2. No entry found and auto type search dialog automatically displayed
3. User enter the search entry and select one of the entries found (either with Enter or with Shift+Enter)
4. Auto type search plugin either executes the normal auto type (i.e. username and password) or what ever is configured as alternative action (including copy password to clipboard but no option available to auto type password)
Oops. I didn't notice that you posted in the auto-type search forum.
The password only option is the last option in the either the normal or alternative action dropdown menus. See the attached screenshot showing the option selected in the alternative action.
Last edit: wellread1 2021-01-18
Weird - I don't have that option. Will try to update the plugin if there is newer version.
Apologies - looks like it was added in the latest version of plugin. I was using the version just before that one.