When I use BW to complete a pw via suggestion when registering for a new account, I expect to find that pw saved in BW afterwards. I just used BW to sign up for a new Protonmail account. Afterwards, I cannot find any record of that suggested pw or the new Proton account.
Am I doing something wrong here? How should this work on BW? [1P convert here].
I am sorry this happened to you. Besides bugs related to this that have recently been filed, BW has been historically iffy in doing auto-save/auto-modification for login/account creation forms. It’s recommended that you do this manually, essentially doing this (for account creation):
For the proton mail account, there might be a way to recover it. If you have the email/username, but not the password, you can look in “Generator → Password history,” matching the time you created the account. If Proton sent you any kind of confirmation, the timestamp is a good indicator to match the password.
The safest way to register an account on a new website is:
Navigate to the website’s login page.
Open the bitwarden extension and click on the “+ New” button.
Enter the username/email you would like to use the site.
generate a password by clicking on the two-arrow circle icon.
Scroll down to notice that the “Website URL” is filled in.
Click ok to save the account in Bitwarden.
Proceed to the site’s “create an account” page and use auto-fill to populate the username and password.
By first creating the account in Bitwarden it ensures that the Bitwarden entry was completed successfully. By using autofill, it ensures there is not a typo between bitwarden and the website.
Zeb,
I feel your pain but you didn’t do anything wrong, The extension only has focus when your interacting with it so when jump back to the logon page the extension terminates. At a minimum you need to copy the password immediately as the password stays in the copy buffer even if you close tthe extension without saving and you can reopen the extension and paste it to the password field. Cant tell you how many times I’ve had to repaste.
It seems that you and @Zeb are talking about two different issues. Although, to be fair, neither of you have described your workflow in sufficient detail for us to determine what approach you are using when creating a new item, and what is going wrong in that process.
An approach along the lines of what @DenBesten has described is reliable, and unaffected by the occasional vagaries of other account creation methods.
@zeb, I have never used 1password, so I have no knowledge of if the two products are supposed to behave the same.
Bitwarden does offer to save logins. Please make sure that these settings are checked and that the site in question is not in your “excluded domains”.
The reason I use the so-called kludge is that it is reliable. The “offer to save” occurs after you have created the account on the web site. If something goes wrong, you only become aware of the problem after it would have been easy to make a course-correction.
I just edited the title of this thread from “Suggested Keyword Not Saved” (I wondered since yesterday, what keyword that could be…) to “Suggested Password Not Saved” - hope you’re okay with that change.
Hi Den, with 1P, I believe this is how it works: if I generate a pw to use on website, 1P will save that as a password with the URL in the item info in my vault. I can search for the URL to find it, or view my most recently added items and see it there. If I employ 1P to generate a pw during a standard account creation, the modal will persist and ask me to save the entire new login with user id and generated pw.
My experience with BW so far is that it generates a pw and saves it nowhere. If I’m causing this behavior somehow, I’ll be please to learn how to fix it so that generated pws are saved to the app and I can look them up and create a login from them, or just use them again as needed.