Auth Generator lacks support for custom provider

[dthyresson]

See the following Community topic post from "edjiang":

"Looks like we’re not able to generate custom providers anymore?"

While the docs do seem to indicate that one can generate a custom auth provider:

It is not supported because:

https://github.com/redwoodjs/redwood/blob/c46033a5229bdeba5d2549466e416400a22ba2b4/packages/cli/src/commands/generate/auth/auth.js#L35

and there is no "custom" template.

While it may be relatively easy to setup the web side, the api side is more complicated with the changes needed for graphql and the additional auth lib.

The custom generator could (and should) still add these to the api side, and stub on the web side.

[aggmoulik]

@jtoar I was thinking to work on this as there is another Database Authentication coming after this PR, Should I continue or not ?

@dthyresson @thedavidprice

[thedavidprice]

Hi @aggmoulik It's great having you as a contributor. Thanks for keeping it up!

For all intents and purposes, the dbAuth #2701 will be the Redwood "custom provider". So there's nothing more to be done here.

If you're looking for other high-priority issues that get us to v1 and need help now, talk a look at the column On deck (help-wanted) here in the Current Release Sprint project board.

[thedavidprice]

@dthyresson curious about your reaction to my thoughts above — in light of dbAuth provider, do you still think there's value in a boilerplate setup for "custom"?

Regardless, we should clear up the docs.