News for hackers. Stuff that matters.
Re:State of OpenID Connect Providers by vbezhenar on Thursday December 22, 2022 @11:27AM (#34095084)
It's a shame that old OpenID was killed in favour of OpenID Connect. With OpenID I was able to log in to livejournal using OpenID implementation running on my own domain. With OpenID Connect I can only log in with blessed set of providers. Centralization sucks.
Re:State of OpenID Connect Providers by schwap on Thursday December 22, 2022 @11:42AM (#34095302)
The standards for this experience exist with OIDC Discovery[1] and Dynamic Client Registration[2], unfortunately they aren't used but it's not because it isn't supported.

[1] https://openid.net/specs/openid-connect-discovery-1_0.html [2] https://openid.net/specs/openid-connect-registration-1_0.htm...

Re:State of OpenID Connect Providers by kevincox on Thursday December 22, 2022 @12:41PM (#34096067)
Do any big-name providers support this? For example trying the webfinger request described in the first link on gmail.com returns a 404.

As much as I love the ability to use my own server it is going to fall flat for the vast majority of users if you can't support at least one of Google/Facebook/Twitter/Microsoft.

Re:State of OpenID Connect Providers by tlarkworthy on Thursday December 22, 2022 @02:40PM (#34097561)
Re:State of OpenID Connect Providers by tlarkworthy on Thursday December 22, 2022 @02:43PM (#34097609)
Re:State of OpenID Connect Providers by BillinghamJ on Thursday December 22, 2022 @03:04PM (#34097909)
Re:State of OpenID Connect Providers by kevincox on Thursday December 29, 2022 @09:12AM (#34172723)
But that's not the point. The goal of the discovery spec is that the user can enter an email and sign in with an OpenID connect provider of their choice. If I need to do an MX lookup and guess what identity provider they are using it doesn't solve the problem of needing to maintain a list of supported providers.
Re:State of OpenID Connect Providers by tlarkworthy on Friday December 30, 2022 @10:15AM (#34185747)
True, the "well-known" path seems to be in a random location but maybe that's a problem with the spec, you might expect it to be off the root of the email domain.
Re:State of OpenID Connect Providers by dwaite on Friday December 23, 2022 @01:14AM (#34102792)
No. Generally this is because it is not a technical capability problem, but a business problem.

Often, sites which use OpenID for authentication either have no automated account recovery, or do recovery based on a verified email claim. This means those relying parties do indeed rely on the reliability and service support promises of the OP, as well as the validity of attribute data shared.

If ISPs or Google had been interested in providing webfinger-based discovery, we might have been able to create a decent UX around an assumption that your identifier was an email address, and that a local authentication process (including potentially an emailed code or link) was an acceptable fall-back. But there was never really critical mass for this to happen.

Re:State of OpenID Connect Providers by api on Thursday December 22, 2022 @01:28PM (#34096650)
Are you sure that wasn’t the point?

OIDC is the biggest monopoly play in the industry right now and it’s an absolute privacy nightmare. Almost nobody seems to even notice.

Of course history has shown that people will trade literally everything for convenience so it will probably succeed. In the future if you get your Google account locked you won’t be able to access your bank account or buy a plane ticket and Google will know everything you use at all times and be able to log into anything you use. But it’ll be convenient.

Re:State of OpenID Connect Providers by fghjklty on Thursday December 22, 2022 @01:35PM (#34096739)
yes, it was always the point.

Microsoft was the main proponent and gave talks to every single government agency in the world in favour of it. never mentioning OIDC. while google was promoting it left and right to developers. also never mentioning OIDC. Only the open/decentralized parts.

it was the classical embrace, Extend, Extinguish play. By now a classical move of both Microsoft and Google.

Re:State of OpenID Connect Providers by anderspitman on Saturday December 24, 2022 @02:11PM (#34120068)
I wonder if a nonprofit privacy-oriented identity provider could work. All it does is provide OIDC to to any apps that want to integrate. On the backend users can login with any social provider or email, but the social providers would only ever see a login from the nonprofit.
Re:State of OpenID Connect Providers by notatoad on Thursday December 22, 2022 @01:32PM (#34096701)
OpenID supporting any provider would have been nice, but from my limited experience at implementing it suffered from the same issues as this blog post - poor implementation.

OIDC is basically an admission that supporting any arbitrary provider had failed, and you need to actually test with each specific implementation before marking it as being supported.

Re:State of OpenID Connect Providers by zvr on Friday December 30, 2022 @05:15AM (#34183683)
As someone who ran their own OpenID server for a couple of identities but has not touched this stuff for years, I have to ask:

Is there anything today that I can run (self-host) for a similar result?