News for hackers. Stuff that matters.
Re:OpenID Connect specifications published as ISO standards by simonw on Sunday November 10, 2024 @03:51PM (#42102558)
My problem with it being called OpenID Connect is that, in my head, an OpenID is a noun which means "a URL that you can use as your identity and prove that you own".

That definition doesn't work for OpenID Connect. Is OpenID a noun any more? I don't think it is.

Re:OpenID Connect specifications published as ISO standards by clhodapp on Sunday November 10, 2024 @04:11PM (#42102648)
[delayed]
Re:OpenID Connect specifications published as ISO standards by pas on Sunday November 10, 2024 @07:37PM (#42103651)
Hm, so the point of adding this additional hop (which is also a JSON under the .well-known/ prefix), is that I can always put the domain of my homepage into WebFinger aware OIDC login boxes, no need to remember the domain of my OIDC provider?
Re:OpenID Connect specifications published as ISO standards by shadowfacts on Sunday November 10, 2024 @09:45PM (#42104223)
Yes. This is how, for example, Tailscale implements bring-your-own identity provider: https://tailscale.com/blog/custom-oidc

It is, to date, the only non-selfhosted service with which I can use my self-hosted SSO setup.

Re:OpenID Connect specifications published as ISO standards by francislavoie on Monday November 11, 2024 @01:12AM (#42104887)
I feel like I remember StackOverflow (and related sites) having OpenID login as an option, but I don't see it anymore. I figure they removed it due to low popularity.
Re:OpenID Connect specifications published as ISO standards by yrro on Monday November 11, 2024 @06:54AM (#42106509)
Sourceforge used to have it too!
Re:OpenID Connect specifications published as ISO standards by Terretta on Monday November 11, 2024 @02:58PM (#42109995)
> removed it due to low popularity

Gotta get that sweet sweet SSO Tax revenue, and justify it by blaming setup and integration expense for SAML?