Can you please confirm you refer to this auth0 SDK?
Is there a compatibility between your appās React Native SDK version and the chosen auth0 SDK (can be checked in the Readme.md )
If Iām not mistaken the authorize method you shared here is to bring the user to the login page to authenticate. What Login page you use? Universal Login / New universal Login / embedded login?
Could share more information on the action youāre working on?
Yes, I am using the SDK that you linked above. Here is my entry in package.json "react-native-auth0": "^2.17.4"
Yes, authorize shows the login page, BUT users can also sign-up form that page. We are using New Universal login.
On Pre User Registration we want to validate an internal-invitation-token (token generated by our system when inviting a user to one of our tasks). We also want to verify if there is a similar token on Login.
Hey Franck @fnadeau !
The issue you encounter here can be reduced to IdP not supporting the custom āuser_metadataā parameter in /authorize requests.
The parameter you would like to use (I assume) can be classified as āupstream parameterā which would be sent to IdP in /authorize requests.
Upstream parameters, with some limitations, have to be first set for specific connection (like for example Username-Password-Authentication) via the Management API to make them available for /authorize requests.
It works this way:
There is a preset list of fields that you can map your custom parameter with.
Once you choose the field, use it in your /authorize requests.
Example:
Updating connection with an upstream parameter:
Where: ālogin_hintā is a preset field, and āscreen_nameā is a custom parameter of your choice. Login_hint used in /authorize parameters will be passed as āscreen_nameā to Auth0.
I think you could try with this approach (a guidance with the list of available fields here). Please let me know if that works for you. Thanks!