Set a value property to the Kinde user
Hi guys, I'm looking for some help with this.
Currently the flow we use would be like this:
- The user visits the web app
- If the user does not have a session, it is redirected to the auth provider's access page
- If the auth provider detects that it is a sign up event, it attaches a random uuid v4 to the user properties and communicates to our API to create the user with the uuid that it assigned.
- If everything is ok, the user is redirected to the web app and the uuid is found in the properties of their id token.
So the only way I can think of for this to work with Kinde is:
- Add the property to the user's record
- When the user returns to our web app, check if the user exists or not. Negative case create it.
But is there any way to generate in Kinde or add a uuid pre sign up? I still haven't found a way to do it
I understand that an alternative flow would be that once the session is obtained, verify if the user exists, if it does not exist, create it, modify the properties with the uuid assigned by our service through the Kinde API. Refresh the session in the web app
Any ideas for a flow that doesn't include creating custom login/sign up?
Currently the flow we use would be like this:
- The user visits the web app
- If the user does not have a session, it is redirected to the auth provider's access page
- If the auth provider detects that it is a sign up event, it attaches a random uuid v4 to the user properties and communicates to our API to create the user with the uuid that it assigned.
- If everything is ok, the user is redirected to the web app and the uuid is found in the properties of their id token.
So the only way I can think of for this to work with Kinde is:
- Add the property to the user's record
- When the user returns to our web app, check if the user exists or not. Negative case create it.
But is there any way to generate in Kinde or add a uuid pre sign up? I still haven't found a way to do it
I understand that an alternative flow would be that once the session is obtained, verify if the user exists, if it does not exist, create it, modify the properties with the uuid assigned by our service through the Kinde API. Refresh the session in the web app
Any ideas for a flow that doesn't include creating custom login/sign up?
