node-oauth2-server VS node-oauth2-server

View on GitHub

There's a module on npm that abstracts away the "complicated" bits of oauth - you define just the model functions (like, "retrieve access token", "retrieve valid clients", etc.) and integrations into the request/responses with your favourite web framework -- see https://github.com/node-oauth/node-oauth2-server -- this is a fork of another module that was abandoned. I use this in prod.

In general I would agree, but only if u will go with some 3rd party vendor, like Google or Auth0 from okta, implementing oauth resource server is a real challenge even if u would use community https://github.com/node-oauth/node-oauth2-server packages...

(I use the node-oauth2-server library for backend authentication on my personal app.)

NOTE: This project has been forked from oauthjs/node-oauth2-server and is a continuation due to the project appearing to be abandoned. Please see our issue board to talk about next steps and the future of this project.

So aside from that, there's things like oauth-server which does actually allow you to implement an authorization server. So, if you yourself have a database of users that you want third party clients to be able to authenticate against, you can create your own identity server and implement the various flows.... or maybe you have umpteen systems all with their own auth schemes and you want to standardize it - oauth can be used to centralize this authorization.

It's important to know that this far, although you can perfectly build your OAuth2 server from scratch using frameworks, such as the node-oauth2-server, we'll make use of GitHub's capabilities for the sake of simplicity.

you could take a look at https://github.com/oauthjs/node-oauth2-server (you have to do stuff yourself anyways)