Adding a new user id and generated password to 1Password?

Community Member

I am creating a new user id on a new web page. I have the data entry screen open. I enter my e-mail address and my new user name and I then open 1Password and click Password Generator -> Fill to add a new password. I then press Enter or click Continue. I expected it to but 1Password doesn't offer to save this new information as a new Login. Now that I have logged onto the web page with my new credentials, I open 1Password again and see that there is a new entry there with the new password that was created and entered but it is missing the other details that I entered manually, i.e. the e-mail address and user name. To save this as a new login in 1Password, I need to remember those details exactly and add them to the new entry in 1Password. I don't think this is a very good way to do this. Is there a way to make the process of creating a new userid in 1Password easier?

1Password Version: 5.3.2
Extension Version: 4.4.3
OS Version: 10.10.5
Sync Type: Dropbox
Referrer: forum-search:Adding a new user id and generated password to 1Password


  • littlebobbytables

    Greetings @PaulP1,

    We actively try not to save a Login item on a registration page, let me explain why. The registration page is quite unique and usually contains far more information that is required by the login page and thus the eventual Login item you want to store in 1Password. The other reason is the registration page will almost never tell us anything regarding the structure and IDs of the actual Login page. What we will do though is create a Password item containing the password generated and filled by the Password Generator.

    Here is how I see getting the best usage out of 1Password at the moment and is pretty much the steps I take any time I create a new Login item.

    1. You register with a new site and at some point in the process you have 1Password's Password Generator generate a new password for you on their registration page. 1Password will save that password in a Password item that will also record the domain and title of the site to aid in identification.
    2. You then log out of the site if part of the registration process logged you in automatically.
    3. You visit the site's login page and fill in your username. You use the Password item to fill in the password.
    4. 1Password should ask if you want to save a new Login item. Seeing that you're using a password that exists in a Password item it will convert that Password item into a Login item and update any required fields like the username field and specific URL etc.

    It does require you remembering your username though.

    Now we might have a bug at the moment were it doesn't ask if you want to save when you fill using a Password item but will if you copy and paste the password. We are investigating that right now.

    Does any of this help with why and how we envisage it being used?

  • PaulP1
    Community Member

    Thanks for your reply, and yes, it did help.
    I have been trying to use the technique that you described above and 1Password hasn't been doing as you describe in step 4 so I agree with you that you might have a bug.
    I agree that the registration page often contains extra details that are not needed for the actual login but they are also details that are good to remember in case asked later and 1Password would be a good place to do that. For example sometimes on a registration page it might ask for the answer to some personal question that may be used for later verification and these answers are easily forgotten - at least they are by me :-) Could 1Password simply remember the details in all the fields that I fill in and store that in the login entry? I could then go back into 1Password and look through the fields and find what I'm looking for. I have noticed that, after I fill in a registration page and then press 'save to new login' in 1Password, these details are stored and I can see fields, like my userid, and it is then easy to change the field type to 'userid' and that works. The problem that I have seen with this method is that, because the password field is usually changed to asterisks, 1Password stores asterisks as the password.

    Anyway, I understand this can be a difficult problem to solve but I would appreciate it if some more thought was put into the design so that it flows a little easier (and, of course, fixing that bug because if that were fixed it would be much easier)

    Thanks for your work on a great programme.

  • Drew_AG
    1Password Alumni

    Hi @PaulP1,

    Thank you for the feedback! There may have been a bit of confusion on our end about how this should work and how it currently works, and I apologize for that. You're right that 1Password should be prompting you to save Login items when you register for a new account on a website, so you don't lose that info (although it's also true that it's better to save Login items from the same login form you normally use to sign into a site).

    The bug that littlebobbytables mentioned, and that you also ran into (and which we know more about now) is related to the fact that 1Password tries not to prompt to save Logins if you just used 1Password to fill login info on a site. So for example, if you have 1Password fill your login credentials to sign into a site (using an existing Login item), 1Password shouldn't prompt you to save a new Login item. But some improvements to that logic accidentally resulted in the bug, which is that when you use the Fill button in the password generator, you won't be prompted to save or update a Login item when you submit the web form.

    Our developers are definitely working to fix that (and I believe at least part of the problem has been fixed in the latest beta version of the 1Password extension). For now, there's a simple workaround: Instead of clicking the Fill button in the password generator, you can copy & paste that password into the registration form. When you submit that form, 1Password should prompt you to save a Login item.

    I hope that helps, and I'm sorry again about that! If you have questions or need anything else, please let us know. :)

This discussion has been closed.