Authentication: Expose the Netlify Identity Widget's 'signup' functionality

[cannikin]

redwoodjs/repeater-issues#2

[peterp]

We can append it to this PR: #783

[dthyresson]

Since login can accept options, could login({signup: true}) instead invoke open('signup') instead?

https://github.com/redwoodjs/redwood/blob/main/packages/auth/src/authClients/netlify.ts#L14

  login: () => {
      return new Promise((resolve, reject) => {
        let autoClosedModal = false
        client.open('login')
        client.on('login', (user) => {
          // This closes the modal which pops-up immediately after you login.
          autoClosedModal = true
          client.close()
          return resolve(user)
        })
        client.on('close', () => {
          !autoClosedModal && resolve(null)
        })
        client.on('error', reject)
      })
    },

Instead of adding a new "signup" to the AuthProvider?

[cannikin]

Hmmm for Netlify maybe, since Sign Up and Log In are sort of just two views of the same widget, but other providers might have a totally different flow. Seems like they should both get a top-level function to me.

[dthyresson]

@peterp Same as #783.

Should we reuse login or define a new top level signup?

Assume that signup by default will just invoke login for those that don't have provider-specific logic (like with Auth0 universal login not certain the signup tab can be selected by default).

[cannikin]

Is it weird to only have those providers that support a signup flow actually expose a signup function that you can destructure from useAuth()? Not sure if that's expected in JS world. Or maybe they all expose signup but if you actually call it from a provider that doesn't support it you just get a noop and a console message saying it isn't supported?

It feels weird to me to have a function signup that doesn't sign you up, just takes you to login. But maybe that's just me? @mojombo?

[dthyresson]

Auth0 supports defaulting to Sign Up as well as Netlify.

See: https://auth0.com/docs/universal-login/new-experience

You can make users land directly on the Signup page instead of the Login page by specifying the screen_hint=signup parameter when redirecting to /authorize. Note that this can be combined with prompt=login, which indicates whether you want to always show the authentication page or you want to skip if there's an existing session.

Also example here:

https://community.auth0.com/t/how-do-i-link-users-directly-to-the-hosted-signup-page/42520

Note: probably want to support the "New" Universal vs "Classic" Universal.

@peterp and @cannikin Can we decide if

• add signup()
• add options to login() like {signup: true} or {show: 'signup'}

I think I would prefer to have an explicit signup() because I won't remember the options.

The auth client itself would implement. It might just call login with some extract params.

[dthyresson]

Also see issue: #725 to document login/logout options.

[peterp]

My vote is for a signUp function, so that it feels like it matches our current logIn and logOut functions.