How to turn off auto-fill AND submit when multiple logins exist?

coopr

To Reproduce (I'm using Safari, but I'm not sure it makes a difference):

1. Navigate to a web page for which you have multiple logins saved

2. Hit command-\



What happens:

3. The first option on the login list is filled and the form submitted - note that the first option seems to vary, depending on precisely what URL I'm visiting and what URL is saved with the login



What I'd prefer to have happen:

3. If multiple logins exist for a site, command-slash should show me the list of login options, allowing me to pick the correct one

khad

Set the URLs for the Login items to be identical. You should always be prompted since the URLs will [b]all[/b] have the same "precision" then and no one will take precedence. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



By way of example, this was driving me nuts a long time ago with Twitter, but each of my Twitter logins had a different URL saved. Once I set them all to [font="Menlo"]https://twitter.com/[/font] — the http vs https protocol matters too — it has been smooth sailing.



Please let me know how it turns out.

coopr

That worked! Thanks for the suggestion - it took me quite a while to edit all my records, but indeed having identical URLs forces 1PW to not auto-submit any of them.



Now, how about if 1PW allowed me to edit the URL as it was first saving the PW?! To keep this working going forward, I'll have to constantly be switching to 1PW and editing the saved URLs by hand, each time I create a new login for an existing website - anyone else find that annoying? What about a 1PW preference that says "Default to saving the base URL only (eg. www.Domain.com and NOT www.Domain.com/blah/blah)"

khad

That would break Go & Fill if the login page is not actually at [font="Menlo"]example.com[/font] but somewhere "deeper" in the site. 1Password saves all the information needed to precisely recreate the exact login as you saved it. 1Password does not know if you intended to log in at a different URL or if it was a mistake. Adding the ability to edit the URL inline while saving seems like just as much work as editing it after the fact or simply saving the login on the correct page in the first place.



I will pass along your suggestion, though. Thanks for the feedback! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

coopr

Hmm, good point. I'm guessing your users fall into two groups: though that use "Go and Fill" all the time, and those that never use it (I'm in the latter camp ; )



For those in the former camp, your points are valid. For those in the latter, we just suffer to preserve the usage pattens of those in the former. Can you share any usage data? How do your users break out into those two groups?



Thanks again for your help with this!

khad

Unfortunately, I don't have any data to share.



I rarely use Go & Fill myself, but having the login contain the actual URL for the login page is helpful when I do. When I made some mass changes to passwords last time, Go & Fill was a real time saver. Just double-click the the login and change the password. Otherwise, I would need to go to the home page of the site, find the login page, and then fill the login. That's not counting changing the password. The extra steps add up. It also affects folks who use [url="http://help.agilebits.com/1Password3/oneclick_bookmarks.html"]1Click Bookmarks[/url].



Between the various methods for using Go & Fill — from the main 1Password application, within the browser via the ⌥⌘\ keyboard shortcut, and using 1Click Bookmarks — that sort of change would affect the bulk of our customers.



I would also add that the [b]vast majority[/b] of folks don't have multiple logins for sites. This problem only exists with sites for which we have multiple logins. Even those of us who have multiple logins for the same URL only have a limited number of these. I would wager that the greater percentage of your own logins are for unique URLs rather than multiple logins for the same URL. It ends up being an edge case of an edge case.



We never say "never," though.