News for hackers. Stuff that matters.
Re:Using HTTP Basic Auth in 2022 by foepys on Saturday January 01, 2022 @03:14PM (#29762207)
> doesn't work well with password managers, how to new team members learn the password, no easy way to rotate passwords when offboarding

This is where LDAP and similar are really strong. Unfortunately a lot of companies know that and charge big bucks for this simple feature, often hiding it behind "enterprise" subscriptions where you need to contact them for pricing.

It's also the reason why companies love Exchange and the rest of Microsoft's ecosystem.

Re:Using HTTP Basic Auth in 2022 by VTimofeenko on Saturday January 01, 2022 @03:33PM (#29762399)
Technically as far as I understand the client side certificates and signing/revoking them through internal CA solve the same problems.

However I have yet to encounter such setup used in a professional environment for humans. Is the complexity of such approach just too high compared to LDAP and the passwords?

Re:Using HTTP Basic Auth in 2022 by throwawayboise on Saturday January 01, 2022 @06:03PM (#29763806)
Normal users (including some people with graduate degrees in computer science) can't manage client-side keys or certificates, as anyone who has ever had to support users using ssh key authentication knows. So then you have to provide functionality to do this for them in a foolproof and secure way, which is a big bite to chew.
Re:Using HTTP Basic Auth in 2022 by VTimofeenko on Monday January 03, 2022 @04:11PM (#29786955)
Yeah, I figured the end-user support would fall under the abstract "complexity" I mentioned in my original comment. I can build a hotrod in my garage but nobody sane will use it for public transportation.
Re:Using HTTP Basic Auth in 2022 by loevborg on Saturday January 01, 2022 @03:24PM (#29762315)
That's the thing though - I don't want the complexity of Exchange, LDAP, etc. Complexity kills. This is a simple problem calling for a straightforward solution.