4 ms·

I encounter that a lot with passwords. Amazing how many websites break in weird ways when your password manager throws in random symbols...

frickinLasers 6y ago
Even if they have validation built in when you are signing up! How is it possible that they have taken steps to ensure passwords meet their stringent criteria, but the user still ends up unable to log in? Most recently, I've experienced this problem with two of the big three credit bureaus.
- Tagbert 6y ago
  Because they neither know nor care about security and customer service?
wyattpeak 6y ago
This happens with AWS, which I find just incredible. It'll silently accept a password when changing, but fail when you try to log in. I think in that case it might a matter of length, rather than symbols, but I've never put in the effort to pin down the problem exactly, now that my password manager settings work.
- jjoonathan 6y ago
  That sounds pretty typical of AWS though. Like, I caught them doing the "ask for FQDN but reject FQDNs" a couple of weeks ago in either Route53 or something immediately adjacent (i.e. where people who know better should have been involved), yesterday SageMaker stopped launching kernels because of a "known issue" (don't worry, it doesn't meet the definition of downtime though), and today I had to diagnose an unresponsive control panel by opening the console and digging up a REST error response that they didn't bother to handle in any way. Everything about AWS is not merely broken and half-assed, but fractally so, so that even after using a service for years you are still uncovering severe caveats and awkward limitations. Password validation traps fit that pattern to a T.
- ajmurmann 6y ago
  I wonder if it silently truncates long password on setup. When you then submit the full password it doesn't match.
gdhbcc 6y ago
Not just websites, I've had windows services fail because I happened to have a "\" in the password of the service user running it

frickinLasers 6y ago

Even if they have validation built in when you are signing up! How is it possible that they have taken steps to ensure passwords meet their stringent criteria, but the user still ends up unable to log in? Most recently, I've experienced this problem with two of the big three credit bureaus.

Tagbert 6y ago
Because they neither know nor care about security and customer service?

wyattpeak 6y ago

This happens with AWS, which I find just incredible. It'll silently accept a password when changing, but fail when you try to log in. I think in that case it might a matter of length, rather than symbols, but I've never put in the effort to pin down the problem exactly, now that my password manager settings work.

jjoonathan 6y ago
That sounds pretty typical of AWS though. Like, I caught them doing the "ask for FQDN but reject FQDNs" a couple of weeks ago in either Route53 or something immediately adjacent (i.e. where people who know better should have been involved), yesterday SageMaker stopped launching kernels because of a "known issue" (don't worry, it doesn't meet the definition of downtime though), and today I had to diagnose an unresponsive control panel by opening the console and digging up a REST error response that they didn't bother to handle in any way. Everything about AWS is not merely broken and half-assed, but fractally so, so that even after using a service for years you are still uncovering severe caveats and awkward limitations. Password validation traps fit that pattern to a T.
ajmurmann 6y ago
I wonder if it silently truncates long password on setup. When you then submit the full password it doesn't match.

gdhbcc 6y ago

Not just websites, I've had windows services fail because I happened to have a "\" in the password of the service user running it