You can run your own IdP on your network
Comment on Interesting SSH Authentication Mechanism
Xanza@lemm.ee 4 weeks ago
I don’t understand the obsession in integrating everything with OID services, like Google. People already complain all the time about Google watch-dogging them and then integrate every single service imaginable with their Google account. Shit is just weird to me.
gencha@lemm.ee 4 weeks ago
jonathan@lemmy.zip 4 weeks ago
Orgs commonly need idp, fuck managing ssh key auth for hundreds of engineers.
This isn’t aimed at individuals or self-hosters, though you can if you find it interesting enough.
corsicanguppy@lemmy.ca 4 weeks ago
fuck managing ssh key auth for hundreds of engineers.
You can pull the ssh key out of LDAP/AD. We did this 10 years ago. Really slick.
farcaller@fstab.sh 4 weeks ago
I think the point here is moving away from long-lived ssh keys and using whatever IdP you have (enterprise cloud or local oidc) to provide short-term ssh keys. It generally improves the security posture as it’s similar to ssh with certs but less painful to set up.
Xanza@lemm.ee 4 weeks ago
So does requiring all users to phone you ahead of time to get a temporary password that’s only alive for 20 minutes… But that’s also not done because it’s…stupid.
There are dozens of tools and methods (like jumpboxes) which facilitate the authorization and usage of currently available and time tested tools for usage with environments without reinventing the wheel. Stepping away from the unix philosophy is heresy of the highest degree.
It’s not a problem with the tool, only the plumber.
surewhynotlem@lemmy.world 4 weeks ago
Stepping away from the unix philosophy
SSH already allows auth with username and password against a local file. This just moves the file.
ladfrombrad@lemdro.id 4 weeks ago
Mine’s having the lazy arse syndrome of using it to sign in to Tailscale and having other friends/family using their SSO from the Big G to simplify them signing into my Tailnet.
Guilty as charged?
semi@lemmy.ml 4 weeks ago
I think the Google as an identity provider example is misleading. The more common use case will be medium to small companies where several admins/developers need to login to various servers and where manually adding and revoking keys across these servers will be cumbersome.
As the other commenter said, in those cases, the organization would also deploy its own IDP.