3 ms·
In general I agree that LDAP(S)+Kerberos isn't a very good solution for federated ID management, but I'm not aware of anything that's better, that allows sharin
by e12e 11y ago
In general I agree that LDAP(S)+Kerberos isn't a very good solution for federated ID management, but I'm not aware of anything that's better, that allows sharing an id for system logon, email logon, web-app-logon etc easily. Even for a home setup.
> This is important so that it's possible to transfer grains between servers without all the user IDs changing (which probably makes the grain useless, if it stores user IDs at all).
I see only two sane ways to deal with that: map users to GUUIDs (so logins becomes aliases) - or use user@domain (essentially email addresses). Maybe even both at once.
One thing I've been meaning to look into, is Debian's (the projects) new SSO solution, announced here:
https://lists.debian.org/debian-devel-announce/2015/08/msg00011.html https://lists.debian.org/debian-devel-announce/2015/08/msg00...
Source code here: http://anonscm.debian.org/cgit/debian-sso/debian-sso.git/tree/ http://anonscm.debian.org/cgit/debian-sso/debian-sso.git/tre...
> One thing we want to add, for example, is public-key login, where your identity is your public key fingerprint.
Uh, see above. Even ssh doesn't do that - it binds a key to a login. Building on top of ssh certificates might be a way - but not really for web-apps I think. I shudder to imagine how one would try to handle ssh-keys securely via the browser, that has bad enough support for X509 certificates.
In general I think these are two problems, were one might be a superset of the other: Allow users to set up federated/centralized login/authentication and authorization for all systems, including system login (the system login screen, console login) - the other being allowing users to integrate with an SSO for web apps.
Ldap generally allows for both of these, while other solutions, like eg: facebook-login doesn't in the general case make sense for system login.