Custom signup about docs HOT 6 CLOSED

@glena could you copy at least here the complete redirect example of custom signup?

from docs.

@cristiandouce: I think we just need to add a brief description of what is needed to change in you want another approach and most common issues.

IE:

• remove the callback of the login call if you want to be redirected
• set window.lock.getClient()._callbackOnLocationHash to false if you want to use the 'code' workflow
• setup the callback and allowed origin (CORS) domains in the app

Anyway, I will update it as soon I finish another thing. It was to avoid forget updating the doc.

from docs.

@cristiandouce do you think it is clear? (check the notes section at the end)

https://github.com/auth0/docs/blob/update-custom-signup/content/custom-signup.md

from docs.

do you know @rolodato work on this?

from docs.

This is the example using APIv2 I was making: https://github.com/auth0/auth0-custom-signup-apiv2-sample

However, we discussed this with @dschenkelman and the greatest issue we found is that user signups are not atomic. It requires two requests, and if the second one fails it can leave the user in an inconsistent state.

Adding custom fields (passed to user_metadata) in /dbconnections/signup could work, and it's a first step for when we add extensibility on signups.

from docs.

@rolodato The idea is to make clear how it works with the redirect flow.

Added:

• Redirect with hash for SPA
• Redirect with code for server side webapps

APIv2 is another thing.

from docs.