Nested user data not persisted in advanced registration form

[spwitt]

Nested user data not persisted in advanced registration form

Description

Custom user data on an advanced registration form is not persisted if the base key already exists on user.data.

Affects versions

1.4.0+

Steps to reproduce

Steps to reproduce the behavior:

1. Create application App A
2. Create application App B
3. Create form field user.data.foo.bar
4. Create form field user.data.foo.baz
5. Create an advanced registration form for App A that includes the user.data.foo.bar field
6. Create an advanced registration form for App B that includes the user.data.foo.baz field
7. Use self-service registration to create a new user for App A, filling out user.data.foo.bar
8. Use self-service registration to register the user from (7) in App B, filling out user.data.foo.baz
9. The user.data.foo.baz field is not populated on the User object

Expected behavior

1. Both the foo.bar and foo.baz user data fields should be populated after the user has registered for each application.
2. The user should not be allowed to complete registration if required fields are not populated

Platform

• Device: Macbook Pro
• OS: macOS
• Chrome 112
• PostgreSQL 15.2

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

[spwitt]

Internal

• https://github.com/FusionAuth/fusionauth-app/pull/252