bigodon VS node-oauth2-server

You can use Bigodon in your mocks to create templates that are evaluated with request data as context. What you write between {{ and }} allows you to access fields from the context like request.params, request.body, request.headers, request.query.

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