3 ms·
For those who are looking for an alternative and are OK with centralization of Auth which is somewhat different from the goals of OAuth, check out the CAS stand
by hardwaresofton 6y ago
For those who are looking for an alternative and are OK with centralization of Auth which is somewhat different from the goals of OAuth, check out the CAS standard -- it's an alternative to SAML more so than OAuth.
It's so simple I wrote (and abandoned) a golang library that implements v1[2]. I didn't need the proxy abilities in v2 (and doubt most orgs actually do) and I use JSON in some places before it was in the standard but it was very easy to implement and thus I can say it's easy to understand. I've meant to convert the project to Rust for a long time but at this point I'll probably never get to it.
[0]: https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Spe...
[1]: https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.html https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol.htm...
[2]: https://github.com/t3hmrman/casgo https://github.com/t3hmrman/casgo
- user5994461 6y agoI really wouldn't advise to use CAS in 2020. It's an historical curiosity that stopped being relevant some years ago. It's an old protocol to do single sign on within a company. It worked well and I've seen it used in large companies circa 2010, allowing to support sso in their internal web applications, for employees. CAS is irrelevant now. The world has standardized on OpenID Connect (and SAML as second choice). Anything that's on CAS was migrated or is pending migration to OIDC. As a developer you will have to deal with OIDC (and maybe SAML) for integrations with google auth, facebook auth, microsoft active directory. You really don't want to go for a dying ecosystem (CAS), that's a dead end for your career.