Hello! We are using Auth0 as an IdP for SSO to Thinkific (https://www.thinkific.com/) using OpenID Connect. Thinkific requires the root attributes
family_name to be set on the user.
We use the Universal Login Classic Experience. When the user logs in using Google, these attributes are properly set and it works just fine. However, when the user logs in using GitHub or email/password, these attributes are not set and the login fails.
Is there a way to ensure that these root attributes are always set for users when they sign up, even with dummy values (we don’t actually need their names)? I looked into using the pre-user-registration action trigger, but it seems that the API object there only allows editing
app_metadata, but not root attributes like
I also found this page in the docs: Set Root Attributes During User Signup
However, it seems that this page covers the case when we are creating the user manually and not when Universal Login Classic (which seems to use Auth0 Lock under the hood) initiates the user creation for us. In a similar fashion, I could use the Management API to update the user post-signup, but apparently that specific trigger is non-blocking, so I’m worried that by that point Auth0 would have already sent the user data to Thinkific with the attributes still missing.
I am currently looking into 2 potential solutions to update the user after they sign up / log in, but before their data is sent to Thinkific, which I’m not sure will pan out:
- Using one of the blocking action triggers (maybe the post-login one?)
- Customizing the Auth0 Lock configuration in the Universal Login Classic page
I would greatly appreciate some pointers, even just confirming/denying whether or not I’m on the right track would be helpful.
Thank you in advance!