6 ms·
OpenID Connect specifications published as ISO standards
- styczen 2y agoI search 2 years ago a working server and not found ;(
- personality1 2y agoHave you tired https://www.keycloak.org/ https://www.keycloak.org/?
- dathinab 2y agoIn my experience KeyCloak can be a very mixed bag. And if you are especially unlucky might be so painful to use that you could say it doesn't work. But for a lot of use cases it does work well. In some context it might safe you not just developer month, but years (e.g. certain use cases with certification/policy enforcement aspects). But it also can be a story from running from one rough edge into another where you project lead/manager starts doubling or tripping any time estimate of stories involving Keycloak. E.g. the REST API of Keycloak (for programmatic management of it) is very usable but full of inconsistencies and terrible badly documented (I mean there is a OpenAPI spec but it's very rarely giving you satisfying answers for the meaning of a listed parameter beyond a non descriptive 3 word description). (It's also improving with each version.) Similar multi tenancy can be a pain, depending on what exactly you need. UMA can be grate or a catastrophe, again depending on your specific use cases. SSO User management can just fine or very painful. There is a UI for customizing the auth flow, but it has a ton of subtle internal/impl. detail constraints/mechanics not well documented which you have to know to effectively use it so if you can't copy past someones else solution or only need trivial changes this can be a huge trap (looking like a easy change but being everything but that)... The build in mail templates work, but can get your mail delivery (silently) dropped (not sure why, maybe some scammers used Keycloak before). The default user facing UI works but you will have to customize it even if just for consistent branding and it uses it's own Java specific rendering system (and consistent branding here isn't just a fancy looks goal, one of the first things though on scam avoidance courses for non technical people is, that if it looks very different it's probably a scam and you shouldn't log in). I think Keycloak is somewhat of a no brainer for large teams, but can be a dangerous traps for very small teams.
- twobiers 2y agoI cannot agree more on the very mixed bag. In general, Keycloak is a very solid Authorization server. There is a very active community around Keycloak, and if one need an authorization server, they should consider picking it. We use it in an internal multi-tenant environment as a central customer authentication platform. BUT there's also a lot of pain in using Keycloak, especially when you build on top of it. One of the great things about Keycloak is, that it can be seen as an extendible platform. Nearly everything is customizable. However, it takes a lot of time and effort to learn the programming model and especially the documentation is a PITA. It has been even worse 2 years ago, but it's still a lot of fiddeling around and usual I find myself in reading the Keycloak source (which has a very mixed quality btw.) as no documentation is available. Multi tenancy is indeed also a hard topic. We heavily utilize multiple realms (I think we should have hit 100 already) for that, but newer developments in Keycloak now offer an additional model based around organizations [1]. One thing that bothers me personally is that the storage model of keycloak does not offer zero-downtime migrations and the work on refactoring it has been paused for now. Since we have a solution based on Keycloak, we deploy Keycloak regulary with every feature. However, the embedded infinispan cache makes this hard on scale as during redeployments Keycloak become unresponsive due to cache leader synchronization and eventually drops some caches, leading to user sessions being terminated. Fortunally Keycloak finally has support for an external Infinispan cache [2] and moved to protocol buffers for serialization [3], which should make upgrades smoother, and grounds the road to zero-downtime deployments. After all this, let me emphasize that for most of it the Keycloak team is aware and is working hard in moving forward. I started using Keycloak with Version 11 and a lot has changed for the better. > I think Keycloak is somewhat of a no brainer for large teams, but can be a dangerous traps for very small teams. I would not agree on that. You don't necessarily need a large team for operating Keycloak and smaller teams are probably not that big of an issue. At least not for operating Keycloak. What I feel to be more a problem is, that many (at least of our) clients are not understanding OAuth 2.0 and OIDC well, and therefore puts a larger burdon on support work. Also there must be at least someone very knowledgable of Keycloak to give guidance to the rest of the team, but in general I would not say it's dangerous. We have even a team operating their own keycloak and using our keycloak to perform OIDC federation (don't ask me why tho, I never understood it). [1] https://www.keycloak.org/2024/06/announcement-keycloak-organizations https://www.keycloak.org/2024/06/announcement-keycloak-organ... [2] https://github.com/keycloak/keycloak/issues/28745 https://github.com/keycloak/keycloak/issues/28745 [3] https://www.keycloak.org/docs/latest/release_notes/index.html#infinispan-marshalling-changes-to-infinispan-protostream https://www.keycloak.org/docs/latest/release_notes/index.htm...
- uj6re 2y agoopen source: keycloak connect2id dex gluu closed source self hosted: adfs hosted: okta (auth0) google microsoft github amazon these are just the ones that were viable 2 years ago
- orphea 2y agoalso open source: zitadel
- mffap 2y agohttps://github.com/zitadel/zitadel https://github.com/zitadel/zitadel
- orra 2y agoThanks, although connect2id doesn't look open source.
- vemgar 2y agoalso open source: Authentik
- mooreds 2y agoAnother closed source option, which can be self-hosted or used as a SaaS: FusionAuth (my employer). It also has a full featured plan which is free if you self host and is available via docker, etc.
- mrweasel 2y agoWe run Apereo CAS pretty successfully. Originally to use the CAS protocol, but now that CAS (the protocol) has been deprecated, we're slowly migrating to OIDC. One sort of weird note about Apereo CAS, OpenID Connect can return data in two format, nested and flat. CAS is the only server I've ever worked with, that defaults to nested. Almost no clients supports this, but the server can be reconfigured to use flat. KeyCloak is also very good, but I'd run is as a container due to the quick release/update cycle. If I had to do our infrastructure over, I'd probably go for KeyCloak, just because it's the most used.
- mooreds 2y agoHmmm. Here's details about using CAS as an OpenID Connect provider: https://apereo.github.io/cas/7.0.x/authentication/OIDC-Authentication.html https://apereo.github.io/cas/7.0.x/authentication/OIDC-Authe... Looks like it doesn't support multiple issuers: " CAS primarily supports a single issuer per deployment/host." Have you run into any issues with that? It also looks like it supports a number of optional standards: DPoP, JARM, PAR. Have you seen use cases for these?
- mrweasel 2y ago> Looks like it doesn't support multiple issuers Yeah, we only have the one issuer, so it's not a concern. For pretty much every KeyCloak project I've done, we have also favored doing separate deployments for separate issuers, so I'd say it's not much of an issue, in most cases. Regarding the optional standards, no. We've not run into an clients that would require or in many cases even support anything but the most basic OpenID Connect. I'm sure there's a point to supporting them, but I've never seen it being needed for your average use case.
- taberiand 2y agohttps://ory.sh https://ory.sh has an open- source self-hosted option Hydra (and a number of other services)
- paxys 2y agoSweet, one more standard for developers to ignore.
- simonw 2y agoIt 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.
- 2y ago
- lysace 2y agoPay-to-read standards like those of the ISO actively hinder human progress. Please don't encourage this behaviour.
- deleted 2y ago[deleted]
- penguin_booze 2y agoWith C++, the latest draft of the standard is made available for free [0]. My understanding is that the final draft and the official standard are more or less same w.r.t. their material content. I imagine the draft standard for OIDC is also available somewhere. [0] https://en.cppreference.com/w/cpp/links#C.2B.2B_standard_documents_and_drafts https://en.cppreference.com/w/cpp/links#C.2B.2B_standard_doc...
- deleted 2y ago[deleted]
- lysace 2y ago> My understanding is that the final draft and the official standard are more or less same w.r.t. their material content. Details matter. So not so open after all?
- pclmulqdq 2y agoAlmost every standard is like this. If you just want to implement, you take the last draft that's public. The process between that draft and a standard is an extensive review and editing process to ensure that wording is exactly precise, patent claims against the standard are void or invalid, and that there are no other problems. That stuff takes time and money.
- halJordan 2y agoNot every MUST be black and white. It is okay to admit things are grey. Those engineers are not actively harming human progress by creating human progress, and its insane to say that
- nick238 2y agoStandards are nice, but the large standards organizations like ISO annoyingly charge a bit to view them. I suppose this is because some businesses/industries require "real" standards by those orgs rather than the IETF or other dirty open-source hippie collectives.
- pyuser583 2y agoThey claim it’s to provide access and funding to undeveloped parts of the world.
- lysace 2y ago:-)
- urbandw311er 2y agoNice one
- pclmulqdq 2y agoMost standards are low priced enough that they are sold at a loss. If you would prefer to donate to ISO (or the IEEE for another example) instead, that would help allay the cost of writing a standard.
- 8n4vidtmkvmk 2y ago"Standard" and "costs money" feel at odds with each other. If you want something to become standard, as in the standard/most common way of doing something, it has to be abundantly accessible so that it can be widely implemented.
- jogux 2y agoIt's a double edged sword. Actually creating a good standard that people want to use through an open process that aims to be unbiased takes a non-trivial amount of time and hence costs a not insubstantial amount of money. Different standards organisations have chosen different approaches to solving that problem, and although I completely agree and freely available standards are my preferred approach, it is also very clear that ISO standards are well respected and widely used despite the need to pay to view them in some cases.
- bborud 2y agoNo aspect of this is good for anyone. First, standards you have to pay to obtain are a really, really bad thing. Second, I wish more effort would go into designing standards and implementations that aren't such an endless time sink when you need them.
- woodruffw 2y agoI agree about ISO, but I don't think there's a meaningful "toll gate" in this case: the standards are already free and public, this seems to just assign them identities in the ISO's standardization namespace. (I'm at a loss to explain what benefit comes from being assigned an ISO standard versus putting a HTML document on the Internet.)
- mooreds 2y ago> (I'm at a loss to explain what benefit comes from being assigned an ISO standard versus putting a HTML document on the Internet.) From the article: "[ISO certification] should foster even broader adoption of OpenID Connect by enabling deployments in jurisdictions around the world that have legal requirements to use specifications from standards bodies recognized by international treaties, of which ISO is one."
- woodruffw 2y agoThe point was that countries clearly recognize standards that aren't bound to an ISO (or other international standards) process, given that every country in the world uses TCP, HTTP, and HTML. (Unless we're now considering the IETF/W3C an international standards body? I can't find a good list of these anywhere.)
- mooreds 2y agoThat's fair. And this type of standardization is far enough outside my wheelhouse that I don't know how to judge Mike's comments. He's pretty deep in that space, so I take it at face value. I don't think he'd have pushed this effort without there being value. Looked on the OpenID mailing list site[0] and didn't find any discussion, so can't offer any other insight. I suppose you could contact Mike[1] and ask why it is such a big deal)? > Unless we're now considering the IETF/W3C an international standards body? Most of what I know about standards bodies I learned from Heather Flanagan, who is/was active in a lot of these and did a great presentation at Identiverse in 2022[2] about this very topic. 0: https://lists.openid.net/mailman/listinfo https://lists.openid.net/mailman/listinfo 1: https://self-issued.consulting/contact-me https://self-issued.consulting/contact-me 2: https://www.youtube.com/watch?v=YBP8ffezycY https://www.youtube.com/watch?v=YBP8ffezycY
- deleted 2y ago[deleted]
- revskill 2y agoISO means It's so overcomplicated i think.
- jcmfernandes 2y agoSince OIDC is a layer on top of OAuth 2, it inherits its complexity. OAuth 2.1 (currently draft) will help bring some sanity. GNAP - https://oauth.net/gnap/ https://oauth.net/gnap/ - will, one day, tie everything.
- mooreds 2y agoGNAP was just codified to be an RFC: https://www.rfc-editor.org/rfc/rfc9635.html https://www.rfc-editor.org/rfc/rfc9635.html When I looked at it a few years ago[0] it seemed like a modernization of OAuth (which still uses form posts(?!?)). But I'm worried about uptake, myself. Haven't had a single client request it or bring it up. 0: https://fusionauth.io/blog/gnap-next-gen-oauth https://fusionauth.io/blog/gnap-next-gen-oauth
- rapnie 2y agoI see that the GNAP WG has been closed [0]. I don't know how this works with IETF, but is anyone caring for the spec and its adoption atm? [0] https://mailarchive.ietf.org/arch/msg/txauth/uEXUsdk43TbPllsh1pcXXzgvMzk/ https://mailarchive.ietf.org/arch/msg/txauth/uEXUsdk43TbPlls...
- jricher 2y agoThe working group was closed because the core specification is published as a finished RFC: https://www.rfc-editor.org/rfc/rfc9635.html https://www.rfc-editor.org/rfc/rfc9635.html The group's other major work, the GNAP RS specification, has passed IESG final review and is in the queue with the RFC editor. This means that it's finished except for some final text edits and will be a final RFC soon too: https://www.rfc-editor.org/current_queue.php#draft-ietf-gnap-resource-servers https://www.rfc-editor.org/current_queue.php#draft-ietf-gnap... The group closed because it didn't have any more work to do. As for adoption, we've seen it implemented in a handful of spaces around the internet, most of them in places where there are core problems with the OAuth model or GNAP offers cleaner support for some key feature like ephemeral clients or key management.
- benterix 2y agoGreat. So now we have to pay to read them.
- mooreds 2y agoI don't think so. I think they just have the imprimatur of the ISO standards body now. I don't see https://openid.net/specs/openid-connect-core-1_0.html https://openid.net/specs/openid-connect-core-1_0.html going behind a paywall.
- surfingdino 2y agoMaking it an ISO publication makes it an ass cover for procurement. Nobody got fired for demanding compliance with a pile of ISO standards after all.
- spapas82 2y agoOpenID connect is a rather simple protocol. I was able to understand most of it in about a day by reading the specs (https://openid.net/specs/openid-connect-core-1_0.html https://openid.net/specs/openid-connect-core-1_0.html). For anybody that's interested and doesn't want to read these specs, I've written a comprehensive tutorial on how to implement a client for OpenID using simple HTTP requests (https://spapas.github.io/2023/11/29/openid-connect-tutorial/ https://spapas.github.io/2023/11/29/openid-connect-tutorial/). It's using python to do the work but it should be straight forward to implement it in anything you want. Most of the complex stuff is related to decoding and checking the JWT tokens. I'm using exactly this hand written client on a production project to authenticate with keycloak for like a year and everything's working perfectly! PS: I know that there are way too many ads to my site. Unfortunately I haven't found the time to properly configure google ads and haven't found anything better :( Use an ad-blocker to read it.
- mmcnl 2y agoVery interesting and good write-up. PS. Be cautious with using subjective words like "simple". It can be really off-putting as a reader if you think something is difficult and the author claims it's simple.
- lurking_swe 2y agoeverything is relative. I believe it’s “simple” compared to other standards like SAML. I agree it can be a little intimidating for a novice in the space!
- spapas82 2y agoProbably I should have said "simple compared to oauth" :)
- hackandthink 2y agoA great tutorial. I'm still not convinced that OIDC is easy. Keycloak hides enormous complexity and that's not because the developers were bored. One example is the huge number of settings for various timeouts: SSO timeouts, client timeouts, various token timeouts.
- koito17 2y agoI fear this will be as adopted as PDF/2.0, the first non-free (and ISO) specification of the PDF format. Hopefully the draft versions are freely available somewhere and closely resemble the final product^W specification.
- alasr 2y agoJust found the following on PDF 2.0 (announced on April 5, 2023): https://pdfa.org/announcing-no-cost-access-to-iso-32000-2-pdf-2-0/ https://pdfa.org/announcing-no-cost-access-to-iso-32000-2-pd... Still, I agree with your main point: let's hope future OIDC ISO spec(s) is/are still freely available in some form.
- anilakar 2y agoGreat. Now I need to pay for a huge pile of toilet paper to prove compliance.
- deleted 2y ago[deleted]
- sundarurfriend 2y agoThe link through to PAS says: > Publicly Available Specifications have a maximum life of six years, after which they can be transformed into an International Standard or withdrawn. So is the plan to transform this into a standard after that period? Was a PAS application chosen because (it sounds like) it goes through the standards body quicker? So this gives an intermediate ISO seal of validation until this becomes a full International Standard?
- sunshine-o 2y agoIs there an independent OIDC issuer (outside of Google, MS or Apple) left one can create an account on? I wanted to open an account on Tailscale without using my Github account the other day but couldn't. I believe openid.net and Ubuntu One were providing this service a long time ago but they discontinued it.
- jogux 2y agoThere at least a few others left, https://gitlab.com https://gitlab.com is one I regularly use. Sadly the amount of money you need to spend on security & support for such a service does make offering such a service (particularly for free) not viable for smaller entities, there are some big economies of scale to make these things viable that work particularly well if you can also get big companies to pay for commercial offerings.
- wdb 2y agoGuess great way to spend the last bits of money of the yearly department budget so you won't loose it in 2025
- kuon 2y agoISO is non free garbage which is not helping the software ecosystem. Take ISO 8601, it is overly complicated, not implemented correctly most of the time as maintainers used a free draft and it does not actually solve anything properly. (For example you cannot represent wall clock which is a problem for dates in the future as time zone changes). I also worked with mp4 in the past only to realize that the ISO was not enough as Apple had some changes in their stack.
- deleted 2y ago[deleted]
- 8n4vidtmkvmk 2y agoAre there any alternatives to iso8601? My only beef with it is that there seems to be more than 1 way to represent a few things. Didn't know about the wall clock issue. I wonder if the new JS temporal API handles that.. they went pretty deep.
- kuon 2y agoRFC 3339 should be preferred to iso, but it does not solve the wall clock issue. In a calendar application I worked on, we use city name and lat/lng + "naive" timestamp (yyyy-mm-dd hh:mm or moon based date or other specialties like Japanese year depending on the locale). And we "resolve" to UTC + offset when the date is close. https://news.ycombinator.com/item?id=37339535 https://news.ycombinator.com/item?id=37339535 https://www.mooncratertycho.com/the-12-lunar-calendars-still-in-use-around-the-world/ https://www.mooncratertycho.com/the-12-lunar-calendars-still...
- 8n4vidtmkvmk 2y agoNice! https://i.imgur.com/vsC2Wyd.png https://i.imgur.com/vsC2Wyd.png See even RFC 3339 seems unnecessarily lax. You can use _ or lowercase t or space as the date and time separator? Why? Just pick one instead of complicating all the parsers. The intersection of the two specs seems pretty good though.
- friendzis 2y ago
- ilidur 2y agoReview: Mike Jones is one of the 3 members of the OIDC working group. He celebrates the publication of the spec as a publicly accessible standard (PAS) and has worked to include the erratas so that it is a complete document. Congratulations to the achievement that is OIDC!
- flanked-evergl 2y ago> publicly accessible standard (PAS) ISO standards are not publicly accessible standard. OIDC was always publicly accessible, now I dunno. ISO OIDC is and will be meaningless. ISO is a racket to keep people with no useful skills employed and the organization should be fined for the tax payer money they took and should be sanctioned by every nation in the world.
- drdaeman 2y agoIdentity provisioning is an abomination that shouldn't have been invented. I used to be a fan back in mid-'00s, self-hosting an OpenID server, without realizing how the whole concept is so fundamentally flawed. Identity is an innate and inalienable property of individual, not something that anyone else (another person, company/website, government or whoever else) can "provide". They can merely attest by providing a credential, by e.g. issuing a passport. At least Webauthn got this right.
- lolinder 2y agoIs there a practical consequence to this distinction between attestation and provisioning, or is it purely philosophical?
- drdaeman 2y agoFor me personally, it's primarily philosophical - I don't want to be defined by someone else, only confirmed that it's, indeed, me. However, there are practical consequences. There are plenty of stories how people got their Google/Facebook/Apple/... accounts blocked; or domain name lapsed, for self-hosting folks - and thus lost "their" "identity" (quotes for a lack of better words). One can back up their credentials and attestations - losing a password (or a keypair) is preventable, since it's all first-party. One cannot back up a third-party service.
- bloppe 2y agoThis is fair, but I appreciate having an interoperable standard nonetheless. I'm currently designing an auth system based on oidc where the first party service is itself an IDP, but you could also use a third party IDP like Google. So if you're worried about losing access to your Google account, you can use the first party IDP and set up an account, and if you'd rather not set up a new account, verify email, set up 2fa etc, you can just reuse your Google ID. Since they're both standard OIDC flows, it's not hard to support both (and many more)
- 2y ago
- olieidel 2y agoThe whole monetization and organization around ISO standards feels super shady. One lesser known hack is to search the friendly Estonian site [1] for a cheaper version of the standard - they often create their own versions of the standards which much pretty contain the exact same content as the original. Unfortunately, in this case, it seems they only are offering the actual standard at a similar price [2]. Sad dog face. It could be worthwhile to monitor the website to see if they release their own version for a better price in the future. Usually, their prices are ~10% of the original price (one more data point that Estonia does cool stuff). We deal with the rather shady standardization organizations quite a lot as we work in medical device compliance [3]. I've heard all the usual arguments: "But standardization costs money!", "These organizations are doing good work!", etc., etc. No. I completely disagree. If something's a standard, that in my opinion makes it similar to a law - people should be able to follow it, and that requires people to freely access it. The EU Advocate General seems to agree [4]. And there are lots of standardizations which don't rely on shadily offering PDFs for money: ECMAScript and ANSI C come to mind, but the list goes on. [1] https://evs.ee https://evs.ee [2] https://www.evs.ee/en/search?OnlySuggestedProducts=false&query=26131&Otsi=Otsi https://www.evs.ee/en/search?OnlySuggestedProducts=false&que... [3] https://openregulatory.com/accessing-standards/ https://openregulatory.com/accessing-standards/ [4] https://openregulatory.com/maybe-eu-standards-are-becoming-freely-available-soon/ https://openregulatory.com/maybe-eu-standards-are-becoming-f...
- flanked-evergl 2y agoISO should be fined and abolished, and the money it took from taxpayers should be recuperated from the frauds that ran it.
- deleted 2y ago[deleted]
- selfissued 2y agoThe OpenID Connect specifications are and always will be available for free. See where they are available for free at https://self-issued.info/?p=2573&cpage=1#comment-393548 https://self-issued.info/?p=2573&cpage=1#comment-393548 .
- selfissued 2y agoThis is water under the bridge, but it's a bit ironic to me that I had to create an account to comment here. If OpenID 2.0 had succeeded, I would be commenting with my identifier https://self-issued.info/ https://self-issued.info/, which remains a valid, verifiable OpenID 2.0 identifier. You can still comment on my blog with OpenID 2.0 identifiers today. Have at it!
- selfissued 2y ago[dead]
- orcasino 2y ago[dead]