fix(api): preserve null values for unique indexed fields in UserUpdate #5670
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When MongoDB documents with null fields are read, Go's BSON driver deserializes them as zero values (e.g., "" for strings). On update, these empty strings were written back instead of null, causing "document duplicate" errors for SAML users due to the partial unique index on username (migration 77).
This fix removes username and email from the update document when they are empty strings, preserving the original null values in the database.