Add profileData key to UserIdentity #33
Merged
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.
Description
The key
profileData
is present in social Identities (see below), but is not in theUserIdentity
struct. This means that this SDK cannot be used to retrieve social profile data.Here's an example of the key within an account with two identities:
This PR adds a
profileData
field toUserIdentity
with type*map[string]interface{}
so arbitrary schemas of social providers can be deserialized.References
This PR was motivated by this thread on the community forum: https://community.auth0.com/t/identity-profiledata-field-not-in-management-api-useridentity/78948
Testing
Checklist
main
.