2 ms·
I actually did exclude those on purpose, because I think they're somewhat out of scope -- arguably the point of running something like Authelia/Keratin/Dex/Keyc
by hardwaresofton 6y ago
I actually did exclude those on purpose, because I think they're somewhat out of scope -- arguably the point of running something like Authelia/Keratin/Dex/Keycloak/etc is to not write a single line of auth code, even if it's just wiring up a module/component.
That said, here are some more in the space that I personally have earmarked:
- (all-in-one) jsso2[0]
- (all-in-one, embeddable) a12n-server[1]
- (embeddable) node-oidc-provider[2]
- (embeddable) node-oauth2-server[3]
- (all-in-one, embeddable) authboss[4]
- (proxy) vouch-proxy for NGINX[5]
- (proxy) Grant with support for over 200 provider (!!)[6]
[0]: https://github.com/jrockway/jsso2 https://github.com/jrockway/jsso2
[1]: https://github.com/curveball/a12n-server https://github.com/curveball/a12n-server
[2]: https://github.com/panva/node-oidc-provider https://github.com/panva/node-oidc-provider
[3]: https://github.com/oauthjs/node-oauth2-server https://github.com/oauthjs/node-oauth2-server
[4]: https://github.com/volatiletech/authboss https://github.com/volatiletech/authboss
[5]: https://github.com/vouch/vouch-proxy https://github.com/vouch/vouch-proxy
[6]: https://github.com/simov/grant https://github.com/simov/grant
- core-questions 6y agoI am using vouch-proxy as it is a very simple addon that lets me use my existing OpenID Connect compatible IDP for authentication on anything fronted by Nginx. This works really well for services not really designed to have their own auth. The only downside is that it seems to require a second DNS entry for the vouch portion of the process. Awkward configuration in some ways. But, the price is right, and the Nginx config is reasonably clean once you understand what it's doing.