[Bug]: no update event is sent for user registration via social login

[murieletrentini]

What happened?

I have custom fields in my registration form. The values get correctly sent to our backend with the user-create-complete event. Unfortunately that does not work for users registering using social login. There the event is sent without the additional custom content, since the event is fired right after the social login and before the user get's prompted to enter additional data for the registration. The data is correctly stored, when I look up a user whow is registered with a social login in the 'users' section in FusionAuth, so apparently the form works correctly, but no event is sent.

According to the support response I tried adding a webhook for various other events to capture the additional data.

To note, you will likely want to be listening to the registration.update webhook for changes to the registration object prompted by additional fields the user needs to have completed based on what is a required field for self service registration.
In the case of a user entering all these fields "manually" (as part of a registration form) we will create the user and the registration at the same time (thus transmitting all information, including all required registration fields, as part of the user.create and registration.create events).
However, in the case of a social login, the user and registration will be created after the IdP provider returns information via the user.create and registration.create events. However, additional registration will be asked for of the user as part of the complete registration process (if there are additional required fields) and that additional information will be transmitted as part of the registration.update event.

I also do net get any of these events, where I would expect the additional data to appear:

I only ever get a user.create.complete event for social logins

Version

1.57.1

Affects Versions

No response

Alternatives / Workarounds

No response

[brianweber-fusionauth]

Thank you for reporting this issue. We've added it to our backlog for evaluation and prioritization. While I can't provide a specific timeline, we will keep you updated as to when this moves into development.

[robotdan]

We should definitely evaluate if we need to be sending user.create, user.update, user.registration.create, user.registration.update and the corresponding *.complete events when users are created and updated during an IdP login event.