@holly First off, apologies for my very late reply! I’ve got no other excuse than “life happens”. In any case, thank you for your clarifications. I’m starting to understand how the registration/authentication process works.
After much deliberation, we decided to give the Universal Login a go and try integrating it with our Laravel app. But then, there are a couple more things that we’d need clarified, before I proceed any further.
First and foremost, how could one set up Laravel, so that it will persist the user’s extra attributes, as user_metadata, into Auth0’s database? In other words, what’s required so that Laravel is allowed to forward the user’s metadata to Auth0, as soon as the user updates it?
And second, how could that piece of information be retrieved back into Laravel, so that it can be used in .blade views, when needed?
My initial idea was to simply persist any extra info (which I’d mark as optional) of the user in Laravel’s database, along with the user’s mandatory fields, and just retrieve any of those meta fields simply based on user’s sub unique identifier. What do you think, would that be an easier and/or better approach? But then, what about the user-inaccessible metadata, such as the subscription tier, which should ideally go into app_metadata, as per your explanation?
Many thanks!