Onscreen, virtual keyboard on login page

iphoneuser

Bank and credit card websites seem to be trying very hard to defeat 1Pass. My credit card info site went to a new log in process, described as follows

i) first page, two fields, one for credit card number (to enroll) and one for username (to login). The field names (or references or whatever they are called) are different if I look in the page source. But 1Pass insists on putting the username in both fields. It also won't automatically submit (I have to click on the Login button).

ii) second page; a field for the password and an online keyboard for a four digit "personal security code". 1Pass fills in the password correctly but can't seem to deal with the online keyboard. ALso, it does manage to submit the form (I don't have to click Login) but of course there is an error.

iii) first time using a machine (or after deleting cookies, I assume) there are two security questions about maiden name and such. 1Pass gets these right and submits the form.

Is there any hope for dealing with the personal security code (online keyboard)? As a consolation prize, I wouldn't mind if 1Pass managed to submit the first form, i), automatically.

Still loving 1Pass. My credit card issuer, not so much.

Thanks.

khad

Could you please provide the URL? I would love to take a look at the site and get this sorted out for you.



Thanks!

khad

Thanks for sending me the URL, iphoneuser! I can see that the [url="https://uiccu.mycardinfo.com/"]UICCU[/url] website is using an onscreen keyboard for the second part of the second page of the login process. What I have done is saved two Login items for the site: one for the first page where you enter your username and one for the second page. (This is outlined in our "[url="http://help.agilebits.com/1Password3/multi_page_logins.html"]How to create multi-page Logins[/url]" guide.)



Now, I tested this using our Chrome extension which is using our latest form filling code. It may not work as well in Safari or Firefox, but the code from our Chrome extension will eventually be making its way into the other extensions. If you have any trouble, please sit tight while we work to bring the functionality to our other extensions or...try Chrome if you like. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Please try saving the login manually like this:



1. Enter your username on the first page, but DO NOT submit the form.

2. Click the 1Password button in your browser's toolbar, and choose Save Login.

3. Name the login item something like "UICCU - Username" and click the Save button.

4. Click the "Login" button on the web page.

5. Enter your password and personal security code, but DO NOT submit the form.

6. Click the 1Password button in your browser's toolbar, and choose Save Login.

7. Name the login item something like "UICCU - Password" and click the Save button.



Now, open 1Password and edit the second login item you created. Change the "Submit" value from "If Autosubmit is ON" to "Never". This will allow you to have 1Password fill the password but give you a chance to click about on the onscreen keyboard before manually submitting the form.



1Password can fill some of these onscreen keyboards, but they are all coded differently. I guess it is better to have a password field that 1Password [b]can[/b] fill (where you can use a password from 1Password's built-in Strong Password Generator) rather than [b]only[/b] having a password field you have to click around on (which ends up reducing security since no one wants to click around on those things very long so they end up with a much shorter password than the ones that 1Password can save and fill for you).



I hope that helps. Heck, I hope it [i]makes sense[/i]. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol:' />



Essentially, 1Password can fill and submit the first (username) page without problem. For the second (password) page, 1Password can fill only the username. Disabling autosubmit for that login item gives you a chance to take over where 1Password leaves off.



I'll pass this URL along to the developers to see how we can improve our code here. Some of these financial sites don't make it easy, but our developers are pretty crafty.



Please let me know if there is anything else I can hep with.



See also: [url="http://forum.agile.ws/index.php?/topic/4596-treasury-direct-treasurydirectgov/"]the Treasury Direct thread[/url] for some additional commentary on these onscreen keyboard dealies.



Cheers,

iphoneuser

Thanks for the detailed response. I can basically get this to work but I don't think it is working quite as you described. I followed your steps but the first page (with the username) will still not autosubmit. Not a big deal. But on the second page, I can't stop the page from submitting (there was no "submit" or "autosubmit" fields to edit; just the "btn" fields for "continue" and "cancel"). I have to open 1Pass and use the copy function to login.

I will wait for the Safari updates and leave Chrome for another day.

Thanks again.

khad

Drats. It sounds like he pages are submitting in the exact opposite manner in which you wish they would.



Autosubmit may not be working properly for the page in Safari at the moment. This should be resolved in the new Safari extension. I'm sorry I don't have a time frame for a specific release right now.



To get the second page to stop submitting, try editing the Submit value. The Submit value is in a drop-down menu:



[img]https://img.skitch.com/20110614-fskkcrmmuamtb93chyegdk3667.jpg[/img]



Please let me know how it goes!

iphoneuser

I was just about to edit my reply when I saw your response. I did see the "Submit" options in the saved login and changed it to "Never". It now works (more or less; I still can't get the first page to autosubmit). I was also able to add a third login item to handle the security questions that come up when a computer is being used for the first time.

1Pass is working well for me but I welcome any improvements.

Thanks for your time.

khad

I'm glad we got that autosubmit issue resolved on the password page. The autosubmit issue on the username page is already resolved in the code, so it is just a matter of porting it to Safari in Snow Leopard. We'll keep working hard to make 1Password even better!



Cheers,