6 ms·
It took me an embarassingly long time (given how keenly involved I was in OpenID stuff ~17 years ago https://simonwillison.net/search/?tag=openid&year=2007 http
by simonw 2y ago
It took me an embarassingly long time (given how keenly involved I was in OpenID stuff ~17 years ago https://simonwillison.net/search/?tag=openid&year=2007 https://simonwillison.net/search/?tag=openid&year=2007) to understand that OpenID Connect is almost unrelated to the original idea of OpenID where your identity is a URL and you can prove that you own that URL.
OpenID Connect is effectively an evolution of OAuth.
- mrweasel 2y agoMy understand is that OpenID Connect is build on top of OAuth2, sort of a specialization.
- jcmfernandes 2y agoCorrect. OAuth is for delegated authorization. OpenID Connect for authentication.
- mooreds 2y ago> OAuth is for delegated authorization. Have you ever seen OAuth used alone? I'm looking for examples of this and they seem to be few and far between.
- anon84873628 2y agoWhat do you mean? What is an example of it not being used alone?
- mooreds 2y agoI mean it is usually paired with an id token, an identifier like an email address is provided, or the access token has a sub claim that is tied back to the user. So it is not pure authorization, but both authentication and authorization. Pure authorization would be like a car key, with no identity mixed in.
- jcmfernandes 2y agoThere are LOTS of them. Anything that allows you to link your Google/Facebook/etc. account to another system, so that system can perform actions on your Google/Facebook/etc. account on your behalf. Examples: Slack (e.g., notify you of events on your calendar, create a GMeets meeting), services like cal.com, whatsapp (store backups on your Google Drive).
- hirsin 2y agoIt's rare in my experience. We don't support OIDC, so technically it's standalone oauth. In reality there's of course a user identity in the mix used to authorize the resulting access tokens. Even server to server calls, ie daemons, service principals, what have you, still rely on a client identity. I think the closest to true agentless access I've seen widely used are SAS for Azure Storage and of course deploy keys in GitHub, which we're building off ramps for. Agentless authz just is not a good idea
- deleted 2y ago[deleted]
- trissylegs 2y agoCanva's api uses oauth2 but not OIDC.
- alasr 2y agoYou may already know this, I'm writing it as a note for my future self. OpenID Connect (OIDC) is mostly concerned with authentication. On the other hand, OAuth (or, to be more specific, OAuth v2.0) is concerned with authorization. >> OpenID Connect is effectively an evolution of OAuth. In my opinion, OpenID Connect is actually evolution of OpenID – in its vision/spirit: - OIDC, like OpenID, primarily focuses on users' identity and authentication; - OIDC, unlike OpenID, didn't (re)invent new authentication workflows, which were significantly different in their own ways. Instead, it built authentication workflows on top of existing OAuth spec (which was being (ab)used for authentication in some places which, unfortunately, is still the case) to achieve its main objective (i.e. authentication). --- Edit: rephrased to better communicate my thoughts (still not perfect; but, as the saying goes, perfect is the enemy of the good so I stop here).
- wtallis 2y ago> OIDC, unlike OpenID, didn't (re)invent new authentication workflows, which were significantly different in their own ways. Instead, it built authentication workflows on top of existing OAuth spec Didn't OpenID predate OAuth? What should OpenID have built upon?
- alasr 2y ago>> Didn't OpenID predate OAuth? What should OpenID have built upon? Yes, you're right about "OpenID predate OAuth" part. However, from my point-of-view, it seems the main source of confusion here is due to the fact that the word OpenID is used in more than one sense: - First, OpenID used as part of the original OpenID authentication protocol developed around 2005 which communicates the idea of a decentralized online digital identity where one way a user can asserts their online digital identity is via a URL under their control. - Second, OpenID used as part of the compound noun in "OpenID Connect" (which as per Wikipedia is "third generation of OpenID technology", published in 2014[1]) which implements the user identity and their authentication via authentication workflows built on top of OAuth2 spec. Now, in my comment earlier i.e. "OIDC, unlike OpenID, ... built on top of existing OAuth spec ... to achieve its main objective ...", I was using OIDC (with "OpenID") in the second sense in comparison to the original OpenID authentication protocol where OpenID is used in the first sense (with both senses mentioned above). I hope it helps. --- As an aside, looking at all the comments about "OpenId" and "OpenID Connect" as nouns, I'm reminded of the following post: Two Hard Things[2] --- [1] - https://en.wikipedia.org/wiki/Openid#OpenID_Connect_(OIDC) https://en.wikipedia.org/wiki/Openid#OpenID_Connect_(OIDC) [2] - https://martinfowler.com/bliki/TwoHardThings.html https://martinfowler.com/bliki/TwoHardThings.html
- antod 2y agoYour talk at webstock back in 2008 is what originally got me interested in OpenID.
- mooreds 2y agoYeah, it's a profile on top of OAuth, which leverages aspects (the authorization code grant, tokens) but adds some other functionality (another token with authentication information and some defined claims). I'm not aware of any other profiles with anywhere near the uptake of OIDC. There are a few folks out there doing pure OAuth, but much of the time it is paired with OIDC. It's pretty darn common to want someone to be authenticated the same time they are authorized, especially in a first party context. I wrote more on OIDC here: https://fusionauth.io/articles/identity-basics/what-is-oidc https://fusionauth.io/articles/identity-basics/what-is-oidc
- dathinab 2y agoAlso interesting is that OAuth2 is a bit too flexible in how you can put things together and OIDC provides a lot of good practice about that how. So even systems where OIDC compliance is a non goal often are partially OIDC compliant, I mean there really is no reason to reinvent the wheel if part of the OIDC standard already provide all you need.
- clhodapp 2y agoOAuth 2.1 tightens it up a bit. I don't think very many people know that OAuth 2.1 exists, though.
- portaouflop 2y ago2.1. is still in draft stage.
- dathinab 2y ago2.1 is mainly updating 2.0 with various later RFCs and usage recommendations, many of them are not drafts. And some document used e.g. https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics https://datatracker.ietf.org/doc/html/draft-ietf-oauth-secur... are technically a draft but practically a "life" document constantly kept up to date So while technically 2.1 is a draft, practically not following it means not following best practices of today so while you don't have to meet it fully if you care about security you really should use it as strict/strong recommendations. At least _longterm_ not doing so could be seen as negligence for high(er) security applications. The most important changes are listed here https://oauth.net/2.1/ https://oauth.net/2.1/
- unscaled 2y agoOIDC is still far more flexible than I would have liked. It still allows the implicit flow, and it even created a new abominations that didn't exist in OAuth: The Hybrid Flow. If you just want to follow best practices, OAuth 2.1[1] or OAuth Best Current Practices[2] are far better options. [1] https://oauth.net/2.1/ https://oauth.net/2.1/ [2] https://oauth.net/2/oauth-best-practice/ https://oauth.net/2/oauth-best-practice/
- lifeisstillgood 2y agoIs it a question of how bad OAuth 2.0 is then? “”” David Harris, author of the email client Pegasus Mail, has criticised OAuth 2.0 as "an absolute dog's breakfast", ””” https://en.m.wikipedia.org/wiki/OAuth https://en.m.wikipedia.org/wiki/OAuth I keep on trying and failing to implement / understand OAuth 2 and honestly feel I need to go right back to square one to grok the “modern” auth/auth stack
- 9dev 2y agoIt’s funny, I’m the opposite. I love OAuth for what it does, that is, federate permission to do stuff across applications. It makes a lot of cool integration use cases possible across software vendor ecosystems, and has single-handedly made interoperability between wildly different applications possible in the first place. I’d say it definitely helps to implement an authorisation server from scratch once, and you’ll realise it actually isn’t a complex protocol at all! Most of the confusion stems from the many different flows there were at the beginning, but most of it has been smoothened out by now.
- __mattya 2y agoOIDC is what fixes the “dog breakfast” criticism. With OIDC you (in theory) don’t have to write custom modules per provider anymore.
- kodama-lens 2y agoIt would fix a lot of the provider specific aspects of OAuth2, if the spec would be more strict on some claim (attribute) names on the jwt ID token. Some provide groups, some don't. Some call it roles or direct_groups. Some include prefered_username, some don't. Some include full name, some don't and don't get me started on name and first_name. If you implement OIDC you must certainly provide a configurable mapping system for source claim name to your internel representation of a user object.
- 8n4vidtmkvmk 2y agoThat sounds bad. Why would they under specify all that??
- ForHackernews 2y agoThe naming is a complete nightmare. OpenID Connect is an extension to OAuth2 (RFC 6749) that adds an authentication layer (to identify a user) on top of the OAuth2 authorization framework (that grants permissions) Earlier versions of OAuth (1.0 and 1.0a) and OpenID (1 and 2) are unrelated, incompatible protocols that share similar names but are largely irrelevant in 2024. Google with care.
- PeeMcGee 2y agoAlso "OpenID Connect" sounds like some sort of branded product rather than a technical standard.
- 7bit 2y agoNo, OIDC is not an Evolution of OAuth. One does authentication, the other authorization. Two very different, but often intertwined concepts, where that both can also be used without requiring the other.