Hi @rueben.tiow,
Thanks for your response. I actually also ran the same test using the action tester and came to the same conclusion that nothing was wrong with the action itself. The problem is indeed that I’m not getting the name on the incoming event.user
object and so, I believe the problem is upstream from the action.
To answer your question, we use the management client to create the user and then request a password change. The code looks something like this (modified slightly to omit sensitive information):
public createUser = ({ userId, email, fullName, appMetadata}): Promise<void> => {
await this.managementClient.createUser({
email,
name: fullName, // <---
user_id: userId,
password: 'password',
connection: 'Username-Password-Authentication',
verify_email: false,
email_verified: true,
app_metadata: appMetadata
});
await this.authenticationClient.requestChangePasswordEmail({
email,
connection: 'Username-Password-Authentication'
});
}
As you can see, we do populate the name field when the user is created. I know that it works given that the name is present when I view the user in auth0 (User Management > Users
) and it is present in the raw JSON details. The app_metadata fields are also what I expect them to be in the created user details.
The Action > Action Logs
feature that you have in beta shows me my logs as I execute the above code. I’m able to run that snippet manually, and I see that I do not have the name field or the metadata as I explained in my previous post. I therefore believe that either the action isn’t getting all the info being sent to the management API or that something in-between that I’m unaware of may be removing this or prevent this info from getting to the action.
Does the Real-time Webtask Logs Extension
work differently or provide me with some other benefit? As far as I can tell, I get the same result but maybe I’m not using it properly.
Best regards,
Giles