Skip to content

Comment on Easy to use OpenID Connect client and server library written for Goparent

Comments

I’d agree that layers of OIDC should be an anti-pattern but aside from that my experience with OIDC (developing and running it in production) has been nothing short of amazing.

Before OIDC it we had (mostly) SAML but it is a beast by comparison and was limited to enterprise use.

The ability of being able to switch auth out with another identity provider with such ease has been nothing short of a blessing.

Yes some overuse redirects and do weird things but the social ones I’ve used plus Okta and my own home grown ones have all been fine.

MitID (national provider login) in Denmark, is about 2 layers of oidc in of itself (normal oidc and an oauth2). Plus whatever the consumers already have, which is often 1 or 2 as well. They're often used as a layer of abstraction which is a gross misuse of the technology.

As I mentioned previously using it for social logins by itself, is fine in most situations as they're quite mature. And IMO the best and probably intended use case of the technology and there it works quite well.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.