My first exposure to this and supposedly just a two line change to the SSH server configuration.
Anyone set this up on their own servers yet? Just for kicks?
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.
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.
You can run your own IdP on your network
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.
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.
Now with modern config management (sit down, Ansible, you millennial junk) the keys update anyway in about a second.
Definitely looks like a nice improvement. Functions very like cloud provider CLI SSO, but with a generic tool.
I think for an enterprise use case, supporting the use of the groups claim (or other configurable scopes) is table stakes. Although in those situations, I’ve also had to use other tools like teleport that come with other enterprise niceties like full session audit capture and playback.
And while everyone should do their own threat and risk modeling, you’ve now made your ssh connection dependent on an external service that likely needs to reach out over the internet.
This looks a lot like what Smallstep’s open source solutions offer.