Ability to change fields used when saving?

pwhittaker

Heya,



I find 1password frequently saves the wrong info in the username field when it saves a new website's details for the first time. Sometimes it gets confused by the site's registration page, and it doesn't use the right info.



Could I suggest that when 1password pops up the dialog to save the info, you somehow either:



1) let me change which fields are used for username and password, or at least



2) show the info, so I can check its right.



Sorry if this has been pointed out before!

khad

Welcome to the forums, pwhittaker!



1Password will save exactly the form information that is in the code on the page for which you are saving the login. If you save a "login" on the registration page it may not fill properly on the actual login page.



If you are having this problem, please try saving the login (from the actual login page) manually like this:



1. Enter your username and password, but DO NOT submit the form.

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

3. Set the Action field to Create New Login (or to Replace <login-name>, to update an existing Login item).

4. Click the Save button.



In addition to being useful in this situation, manually saving a login can be useful for logins that are either problematic to begin with or were once working but have since stopped. Doing this allows 1Password to refresh everything it "knows" about the page. Login pages often change as websites are updated and this can be a necessary but very useful tip. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Of course, you can always edit the login information in 1Password (Edit > Edit Selected Item) and then expand the disclosure triangle next to "All Fields" to make changes to each and every form field that 1Password has saved from the page. Under normal circumstances a manual save will get all of the correct data automatically, so messing about with these details is not recommended. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_wink.png' class='bbc_emoticon' alt=';-)' />



I hope that helps. Please let me know if there is a specific URL with which you are having difficulty.



Thanks!

pwhittaker

Hi khad, thanks for responding.



I understand one can fix a mis-recording in a couple of ways. There are two problems though:



1. I don't know if 1p has misrecorded the details, since there's no confirmation of the data in the popup dialog.



2. Some websites include registration as part of the shopping cart process, and don't provide a nice clean login page (unless you break out of the cart cycle, a major PITA).



I can't point out some example URLs for which this is a problem - it would take some time to dig them up and confirm they were problematic.



However it's more of an issue with trust. On registration pages, 1P is faced with a lot of data. Understandably it sometimes gets things wrong. But despite this guesswork, it acts as though it knows absolutely, and doesn't ask for the user's verification.



There are so many cart and registration systems that I'd imagine you're playing catch-up a lot of the time.

We're all cleverer than 1password (sorry, no offence!). Why not let people at least have the option to visually confirm that even the user/pass fields are correct?



In the end, if 1p acts confidently but fails, I lose trust in it. I also lose time. Both are bad, and i'm likely to revert to my old, insecure system instead.





.

khad

[quote]1. I don't know if 1p has misrecorded the details, since there's no confirmation of the data in the popup dialog. [/quote]

1Password will save everything exactly as it is on the page for which you are saving a login, so there is not really a need to confirm anything. What you see is what will be saved. If it is a registration page, it will save all the registration page form fields along with the username and password (since even some [i]logins[/i] require more than just those two fields and there is no way for 1Password to "know" if they are required for the login or just part of some other form). 1Password [b]will[/b] ask you if you want to save a Login on these pages just in case, but since it is not actually a Login but a registration page, the correct response would be, "No, thanks, 1Password, this is not actually a [i]login[/i]. It's a registration page." <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



As you suggest, we rely on user interaction to solve this.



The method I use is to (1) register for a site first and then (2) open a new tab to the login page to save the login. If you are using the built-in Strong Password Generator — this is done automatically for you if you are [url="http://help.agile.ws/1Password3/3min_1fill.html"]filling a 1Password Identity[/url] — the password will be automatically copied to the clipboard by default so you can easily just paste it in the login form. It is also stored in your Generated Passwords history (Preferences > General > Display in Sidebar) if you ever need to go back to it.



[quote]In the end, if 1p acts confidently but fails, I lose trust in it. I also lose time. Both are bad, and i'm likely to revert to my old, insecure system instead.[/quote]

This is completely understandable, but please keep in mind that 1Password will only do what you tell it to do.



That being said, the vast majority of sites will work just fine with a "login" saved from the registration page. We are always working to improve 1Password, so aside from the user interaction you mention — already included in 1Password — do you know of a sure-fire way to detect this? It is a problem we would love to solve once and for all. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



And, as always, a sample URL helps immensely. Otherwise, we are just speaking hypothetically, and, while we may have a lot of hypothetical code to solve this problem, real data helps get real code written. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_bigsmile.png' class='bbc_emoticon' alt=':-D' />