Password works when copied, but not filled
Comments
-
When I've had this problem, it was because the web site had a password length maximum that wasn't disclosed to the user. I had let 1Password generate a password that was longer than that. For reasons I don't understand, when 1Password automatically filled and submitted my credentials, the web site rejected the password because it exceeded their length limit. When I copied and pasted it into the password field, it was truncated to the maximum allowable length, and when I then submitted it, it was accepted. So apparently at the beginning, when I was constructing the new, too-long password, that setup page truncated the submission to the maximum allowable length and recorded it that way internally. Very annoying!
Anyway, I don't know whether that might apply to salesforce sites, but it thought it might be worth checking.
0 -
Sites very often do not say the maximum length they accept for passwords (or which symbols they accept, or other restrictions). If you create a password that is too long, sites will often not throw up an error when creating it, but - for technical reasons - you can copy the too-long password but not fill directly.
Could this apply in your case?
0 -
Thanks for the quick response. I changed the password length from 14 to 12, but unfortunately it didn't make a difference. Any other ideas?
0 -
Could the site require an even shorter password length than 12? When I was trying to track down my problem I got a clue by counting the number of asterisks filled into the password field when I tried to submit automatically.
If that's not the problem, the only other thing I could think of for you to try is to recreate your logins manually and see if that helps. The directions for doing that are on this page, Saving a Login manually. Try it for one of your records and see if it helps.
0 -
So I deleted the saved password and recreated it and now it's working perfectly. Not sure this is a bug with 1password... :-)
0 -
Hi @richkline,
I'm glad to hear it's working now! If you're using the same Login item and the only thing that you changed is the password, it sounds like the issue was the one hawkmoth and danco described, although it's hard to tell for sure.
If you run into more problems or have any questions, just let us know. :)
0
