3 ms·
Yup. A LOT of businesses make this worse by having some sort of half-arsed single sign on solution where a single set of employee credentials work in a bunch of
by tialaramex 8y ago
Yup. A LOT of businesses make this worse by having some sort of half-arsed single sign on solution where a single set of employee credentials work in a bunch of systems, but not all systems. If you show their users a site they've never seen before with a login box and say it's somehow related to the business ("Our company's partnership with Hat Box means you may be entitled to significant discounts on a range of hats, check them out today!"), they will type in the credentials they use for that business's core systems, not because they're idiots re-using passwords, but because they genuinely expect that might be what works and other systems they use have reinforced that expectation. You can get a LOT of valid user credentials this way without even really meaning to phish them.
As well as preventing confused end users from putting their site A credentials into site B, WebAuthn prevents idiots from designing a system on site B that expects the credentials from site A. It just doesn't work, you can't make it work, so you have to go back to the client and say "No, as well as being stupid that's also impossible". So you not only protect the users from the actual security problem you stop engineers building things which incur the problem in the first place.