This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

Allow secondary / multiple URLs

<div class="IPBDescription">Feature Request</div>Some website login procedures (for example some banks I deal with). Require you to start your login process at one URL, then click through to another

where you enter your password details. For example, I may go to the homepage www.somebank.com and click some "log in now" button. This transfers me to secure.somebank.com

where I enter my login details. If I navigate directly to secure.somebank.com, without first going to the homepage, it will present some error. This causes some problems with 1Password. If I specify the second URL as that for the password, it will be entered correctly via command-\, but if I click to go to the site from within 1Password, it takes me to the wrong starting point URL. If I specify the first URL, 1Password will take me to the start point, but won't log me in correctly.



It would be nice to have a primary URL within 1Password, where you are directed if you click to log in from within 1Password, but also some list of secondary URLs which are recognized

by 1Password as being legitimate sites where the password can be used.

Comments

  • [Deleted User]
    edited March 2011
    Hi anemo42,



    Thanks for the post, and your feedback.



    We are looking into making it possible to associate multiple URLs with a single Login item with 1Password, to help with exactly this situation, and also for multiple sites that share the same login credentials (often the case in business use, for example). I don't have a timeframe for exactly when this will be available, but it's something we're excited to add.



    For now, we've created a guide on how to use 2 different Login items to handle these multi-page login systems, and you can find this here:



    http://help.agile.ws/1Password3/multi_page_logins.html



    I hope that helps.
  • anemo42
    edited March 2011
    Thanks, this is very helpful.
  • khad
    khad Social Choreographer
    On behalf of Stu, you are quite welcome! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



    If we can be of further assistance, please let us know.



    We are always here to help!
  • Smudge
    Smudge Junior Member
    and just to expand on the multi-page login guide Stu linked to, it might be possible to set up just a single login entry that handles both pages. Most of my 2 page login sites work just fine with the following method.



    After you have created the 'Bank 2' page that keeps your password, go into the 1Password program and look at the fields. Most likely the Bank 1 entry just stores your username and the Bank 2 entry stores your password. Edit the Bank 2 entry and note the name of the field for the password entry (most likely it is just 'password'). Then cancel out of Bank 2 and Edit the Bank 1 entry. Manually add a new field, name it the same as it was in the Bank 2 entry, enter your password for the Field Value, then check the Password column. Save the entry. (If you wish to clean up the fields, often sites will have additional form entries that are unnecessary for routine logins, like Cookie, RememberMe checkbox, etc)



    Now go try to log in to the first page selecting the Bank 1 entry. This will submit your username properly. It will attempt to submit the password entry but since there isn't a password field, it is just ignored. Submit the form and it will take you to the 2nd login page. This time, choose the Bank 1 entry again and it will send the password. Again, trying to send the username field which doesn't exist will just be ignored. Submit the form and see if it logs you in.



    So if that was successful, you should be able to delete the Bank 2 entry and just use the Bank 1 entry for both login pages.
  • brenty
    edited April 2011
    Thanks, Smudge! You are absolutely right! As long as there are no overlapping fields, this is a great way to consolidate those crazy bank logins. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/biggrin.gif' class='bbc_emoticon' alt=':D' />



    I am actually doing this in a couple of cases myself, and have suggested it to customers as well on occasion. The trouble is that in just as many cases, it doesn't work at all. My main bank, for example, has seen fit to give the form field on [i]every[/i] page the "password" designation...I guess to obscure the text that is entered. I don't know. In any case, I obviously can't have 3 separate password fields saved in a single Login item in 1Password.



    It truly is a Wild Wild Web out there! <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol:' />



    ..er...that's not what WWW stands for? <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/huh.gif' class='bbc_emoticon' alt=':huh:' />



    [quote name='Smudge' timestamp='1303420744' post='25338']

    and just to expand on the multi-page login guide Stu linked to, it might be possible to set up just a single login entry that handles both pages. Most of my 2 page login sites work just fine with the following method.



    After you have created the 'Bank 2' page that keeps your password, go into the 1Password program and look at the fields. Most likely the Bank 1 entry just stores your username and the Bank 2 entry stores your password. Edit the Bank 2 entry and note the name of the field for the password entry (most likely it is just 'password'). Then cancel out of Bank 2 and Edit the Bank 1 entry. Manually add a new field, name it the same as it was in the Bank 2 entry, enter your password for the Field Value, then check the Password column. Save the entry. (If you wish to clean up the fields, often sites will have additional form entries that are unnecessary for routine logins, like Cookie, RememberMe checkbox, etc)



    Now go try to log in to the first page selecting the Bank 1 entry. This will submit your username properly. It will attempt to submit the password entry but since there isn't a password field, it is just ignored. Submit the form and it will take you to the 2nd login page. This time, choose the Bank 1 entry again and it will send the password. Again, trying to send the username field which doesn't exist will just be ignored. Submit the form and see if it logs you in.



    So if that was successful, you should be able to delete the Bank 2 entry and just use the Bank 1 entry for both login pages.

    [/quote]