Make oauth2 more general

[gurisko]

The current implementation is not very general:

• assuming ${options.provider}Id field in a database
• updating a user with all data returned by the passport strategy (link)

This could be solved by allowing to specify a provider field in a database and support a custom hooks.

[ekryski]

The second issue is now resolved (yet to be released). I agree, any chance you want to put together a PR for allowing to specify a provider field?

[gurisko]

@ekryski Definitely. I will look into this during the weekend.

[ekryski]

@gurisko still waiting on that PR 😉 🙏

[ekryski]

This is still on the radar. Steps are being made to make it more general and at a minimum you'll soon be able to extend the service to have your own custom logic without having to rewrite the whole module or all of auth.

[ekryski]

This is done and in 0.8-beta. Can be accessed and extended by doing this:

const OAuth2Service = require('feathers-authentication').OAuth2Service

class MyService extends OAuth2Service {

}

app.configure(MyService(options))

It is likely that this is moving to it's own repo https://github.com/feathersjs/feathers-authentication-oauth2