We are using the “Non-Unique Emails” connection and working on the user enablement flow.
However with the document from Auth0, we found that the API POST /dbconnections/change_password does not work with Non-Unique Email connections because it requires a unique email address to find the user account. Users must use flows that leverage the primary identifier to reset their passwords.
So we are stucked in the user onboarding process. In my previous operation, we are trigger the change_password after we create the user with the Management API to let the user setup their own password.
Any recommendation on this for how to bring user to the next step after verification?
I am searching if we can utilise the Auth0 Form to do some custom redirection after the steps of the verification
I would recommend creating a change password ticket for your users during onboarding. This endpoint requires the user_id and not an unique email identifier and you should be able to use this for your use case if you are creating users with the Management API.
Please take note that this endpoint only generates the URL that can be consumed by the user. May I ask what is your exact use case for user onboarding to your application?
In addition, if you are using Auth0 Forms or thing about doing so, you should be able to generate a change password ticket and display it to the user during the transaction.