louketo-proxy VS node-oidc-provider

I know from past discussion here some recommended solutions where thomseddon/traefik-forward-auth, vouch-proxy, oauth2-proxy or louketo-proxy aka Keycloak Gatekeeper. I personally think Pomerium is the most versatile and powerful solution out there, especially if you are on Kubernetes or even Docker. Pomerium doesn't yet have the mature documentation, hence this guide.

I could recommend https://github.com/panva/node-oidc-provider supports most of the oidc/oauth 2 rabbit hole specs.

You can also easily setup an OIDC server in Node using a certified OIDC lib like oidc-provider.

If it's nodejs auth servers you're after, look no further than here. Use it as-is, or as a library to build your own richer app.

You can take a look on node-oidc-provider

SEEKING FREELANCER | Remote | NodeJS Dev with OpenID Connect experience

Looking for a NodeJS developer with OpenID / OAuth 2.0 experience to help with upgrading an OpenID Connect implementation. Specifically, the OpenID service depends on v6 of this library: https://github.com/panva/node-oidc-provider

We would like a review of our current implementation, and help with finishing a mostly-completed upgrade to v7 before we onboard 3rd-parties to our authentication and authorization infrastructure. We estimate the contract length to be between 1 - 2 months, part-time. To apply, send your CV and hourly rate to [email protected]. Please be sure to highlight your experience with the relevant technologies and protocols.

Have you looked for other OIDC/OAuth2 packages. Here's one in Node. That seems very interesting. https://github.com/panva/node-oidc-provider

I'm passing familiar with this area, but not as familiar as I should be...

How does this compare to something like this - https://github.com/panva/node-oidc-provider

Are they addressing the same need? Is Ory looking to get certified in these area? (Is it already?)

I really like https://tools.ietf.org/html/draft-ietf-oauth-security-topics with it's evergreen approach and looking forward to oauth2.1 to sum up the current best practices.

Depending on your use case I have good experience with https://github.com/zmartzone/mod_auth_openidc and https://github.com/panva/node-oidc-provider.

https://github.com/OpenIDC/pyoidc also might be a good choice as security researchers in that area did take a look in it...

At our company, I’ve decided to implement this myself. I didn’t do it from scratch, I’ve used oidc-provider but even so. I can say that since for our product, we couldn’t predict the amount of users, we did end up saving money instead of using another product. But, on the other hand, it forces us to know and learn how to develop there even though that is not our main product focus.

Since panva/node-oidc-provider don't have an interface to derive it and implement our adapter (It's written in pure JS); we must provide required methods through an object or a class. To do this we use adapters/memory_adapter.js as a reference class and implement our adapter logic.