New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passwords longer than 15 characters now allowed #787
Comments
The FAQ says:
So where do get that information from? |
I had the same experience. I used a password > 15 chars on Bricklink yesterday and updated it in Brickstore. As a result Brickstore couldn't retrieve info from our Bricklink store anymore. If both (Bricklink and Brickstore) would have been truncated at 15 chars there wouldn't have been a problem. So I guess Bricklink does allow for more than 15 chars that are used. Changed the password back to 15 chars on Bricklink and both worked fine again. Not proof but it might be an undocumented change. Wouldn't be a first for Bricklink ;-) |
It seems that > 15 are only possible via the new pw-reset mechanism the?. The classic way of changing your PW in the account info (*) is still limited to 15 chars (you cannot type in more) |
That's very well possible, since I originally added a >15 char pwd during the pwd-reset mechanism. I switched back using the same pwd-reset mechanism. Oddly enough you can use those links more than once... |
Closing, as the 15 char limit is still in place on BL. That being said, you can enter a longer password in BrickStore and it will use it (that warning you get in the settings dalog is just FYI). So what you have been running into is this: you reset your PW to something > 15 chars and the reset procedure let you input that. It did however only save the first 15 chars, so the "full" password in BrickStore didn't match. Ergo: that BrickStore warning about >15 char passwords was and still is doing its job perfectly fine |
Bricklink now allows passwords with more than 15 characters, but Brickstore only accept max 15 characters
The text was updated successfully, but these errors were encountered: