IdentityServer VS node-oidc-provider

Its deprecated in favor of Duende Identityserver which introduced a license model.

Tokens usually have a lifetime and they are separate from the user's authentication principals like username and password. Unless you are rolling your own form of token provider (not something that would be recommended) the token creation is handled for you. Take a look at https://identityserver4.readthedocs.io/en/latest/ or if your organization makes under 1M in income a year the free version of what Identity Server progressed into https://duendesoftware.com/products/identityserver

I think Duende (Identity Server) handled the situation pretty well.

https://duendesoftware.com/products/identityserver

> Standard License Pricing

Thanks for your message. No, the idea was not to re-implement OAuth nor OpenID stuff. What I had in mind for the authentication thingy was something like this: https://laravel.com/docs/9.x/sanctum. If we want to go the OAuth/OpenID way, in .NET we have this one: https://github.com/DuendeSoftware/IdentityServer.

He's referring to IdentityServer 3/4, which was open sourced, and was not owned by Microsoft. That 3rd party is commercializing their work (and to be fair, it's a lot of work) as https://duendesoftware.com/products/identityserver , and has a different commercial licensing model.

https://github.com/DuendeSoftware/IdentityServer/blob/main/L... does not seem to square with any definition of "open source" I'm familiar with, and that goes double for having an in-repo file that just says "read this unversioned pdf on some other site"

I would not recommend it. There is a server named Duende identity server which you can host locally.

I don't have a direct answer for your questions but do suggest the canonical OAuth 2.0 implementation may be helpful for your learning too. LMK your thoughts. ➔ https://github.com/panva/node-oidc-provider

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

This library forms the basis of a number of OIDC providers we, err, provide to our users.

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

I am a little confused on how to implement an Auth server in node.js. There are plenty of libs that seem to do just that (ex: https://github.com/panva/node-oidc-provider) and then there's passport, which seems to be a full-fledged authentication framework? Will it serve my purpose or would it be overkill and I should just stick with simple libs like the one I mentionned. I can't seem to understand the difference between the two. Can someone explain?

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?)