Even if all that does work I still need to go through the whole thing next week when it forgets. If I click the other option ("I'll try it later") Passwordless doesn't get activated and the next time I get logged out I have to do this all again.
Then I have to click the "Activate Passwordless" button in the extension window and enter my password & I think submit another Authenticator code, before being forced to log out and back in again (with my PASSWORD, 4 times for those who are counting) to finally get Passwordless to work.
After that, I have to type my password in again, before authenticating with LastPass Authenticator. I then get an error requesting that I acknowledge the login in my email account (The computer name, location, IP etc.
After a lot of trouble deactivating Google Authenticator and activating LastPass Authenticator, I still have to type my password in 3+ times in a row every week or more.(Seriously just bring back that button please) On top of all these, I have never been satisfied with the new "Passwordless" feature that replaced the beloved "Remember Password" button on my password locked desktop computer.The "Share", "Checkmark" and right clicking all work.I am also unable to press the "Launch" button. Inside the standard Vault webpage, I am unable to press the "Spanner" button on password entries to enter the editor.(I have confirmed that there are entries in my vault that match the URL of the site) Pressing the LastPass logo in a username/password field brings up only the "Add A Password" button and no existing passwords for the site.The search bar inside the extension does not find a single password, whereas the one on the vault page works correctly.Then once I put the password in on the site, it asks if I would like to add a duplicate password for the site. It means at the moment, I basically cannot use any of the passwords in my vault, without messing around entering the vault webpage, searching, and right click copying the password. It seems to have started when the redesigned Chrome extension was released. I am also experiencing this issue (among others).
0 kommentar(er)
