4 ms·
Summary of crazy terms in this post: OAuth, OpenID Connect, JWT, OAuth 2.0, OIDC, SAML. I know what what only one of these means (OAuth), and the only thing it
by Aeolun 11y ago
Summary of crazy terms in this post: OAuth, OpenID Connect, JWT, OAuth 2.0, OIDC, SAML.
I know what what only one of these means (OAuth), and the only thing it means to me is I'm in for a world of hurt.
I agree with the author, regardless of whether his terms were correct. It'd be nice to have something safe AND simple to authenticate people with.
- broodbucket 11y agoI agree that setting up federated identity isn't as easy as you'd like, but that doesn't mean saying "OAuth sucks!" is okay when a) it's OpenID Connect in this case and b) he's not really talking about anything that's in the spec, it's setting up with one provider with the wrong tools to do so. There are safe AND simple systems, and you pay per user or per authentication to those companies that provide them. It's security, there's no one-click solution, you've gotta do it properly (which can include paying someone to do it properly for you). Google's OpenID Connect documentation [1] is pretty good, and for the steps that involve code in your application, there's very likely a library [2][3] that does it for you. It'd probably take you a day to put something together without existing knowledge, and then you've got secure federated login using an open industry standard that you can easily extend to add other identity providers. [1] https://developers.google.com/identity/protocols/OpenIDConnect?hl=en https://developers.google.com/identity/protocols/OpenIDConne... [2] http://openid.net/developers/libraries/ http://openid.net/developers/libraries/ [3] http://jwt.io http://jwt.io
- hohenheim 11y agoYour requirement is unrealistic. "safe AND simple" can not be if the problem is inherently complex. Security is complex. Sure there could be third party providers that take care of the complexity and provide a service for you, but then is it safe? You could attempt to do it yourself, but then you loose the simplicity and still you don't know if it is safe.
- spronkey 11y agoWell, to be fair, it wouldn't be all that complex if we just had one standard instead of many many many to learn. I don't find OAuth2 as implemented by most all that complex, and I didn't really find OAuth1 all that bad either. The web UI for persona, on the other hand... Who on earth thought it was a good idea to have a two step for username THEN password!?
- efdee 11y ago> Who on earth thought it was a good idea to have a two step for username THEN password!? I haven't used Persona, but maybe this is because not all users use passwords? Sometimes you use AD authentication, or token generators, or ...
- spronkey 11y agoSure. But what percentage of users would that be? Single digits?
- jorams 11y ago> Who on earth thought it was a good idea to have a two step for username THEN password!? Google, as of a while ago. Persona at least had a good reason for it, with not all users needing to enter a password.
- spronkey 11y agoPerhaps, but it seemed to do a pretty poor job of remembering me... At least with Google, despite them being a pretty poor example of good auth UX, you only ever have to type in your password (+ 2fa code etc)
- sp332 11y agoMicrosoft does the same thing with many of their logins. You put in your user ID, and it uses that to know what server is going to authenticate you and forwards you to it.
- sergiosgc 11y agoIt can be safe and simple to use, while being complex on the identity provider's side of the equation. Mozilla Persona was not simple, introduced a ton of new concepts, but you only had to learn all of it if you were an identity provider. For identity "consumers", you could implement and launch into production within an hour of work.