Manually Update Login?

Mr. K.
Mr. K.
Community Member

How do I manually update a login? The login I have saved in 1Password does not fill in the user name in Safari. I want to manually fill in the user name, and then make 1Password update the login.

Comments

  • hawkmoth
    hawkmoth
    Community Member

    Read about it here.

  • Hi @Mr. K.,

    Hawkmoth's link will help you with manually saving the Login for the site. Please let us know if it doesn't help.

  • Mr. K.
    Mr. K.
    Community Member

    Thanks for that info, but doing that and trying to update the existing login does not help with this login. The "web form details" need to be changed, and the updating doesn't make the changes. The "bad" login works in Firefox, but not in Safari. I solved the problem by creating a new login, and then copying over the saved notes and attachments from the non-functioning login to the new login.

  • Hi @Mr. K.,

    That's strange. The Save a New Login is effectively the same as creating a new Login and updating the web form details as well.

    When you said you created a new Login, do you mean you manually created it in the 1Password app instead of using the extension?

    Is it possible to share the website address with us, so we can see if we can reproduce it?

  • Mr. K.
    Mr. K.
    Community Member
    edited January 2015

    I created the new login by using the Save New Login command. I manually filled in the user name and password fields, and then did the Save New Login command. The site is Target Benefits. Note, like I said it works in Firefox, but not Safari, and the new login works in Safari, it's the old login that does not work, and will not update. Here's the URL:
    https://beplb03.portal.hewitt.com/web/target/login?forkPage=false

  • Hi @Mr. K.,

    I tested the site and I can confirm the problem. 1Password can't see the username for some reason and that's why saving it doesn't work. The site is doing something weird in the way it process your username.

    I'll file a bug report to see if we can fix this in a future update to our extension.

    Thanks for reporting this!

This discussion has been closed.