Deprecate methods related to updating user attributes using the Management API #815
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.
📋 Changes
This PR marks as deprecated the
patch(_:attributes:)
method of the Management API client, as it's no longer possible to update user attributes such as email and password from native clients.Also, the respective methods of the
UserPatchAttributes
class –taken as input by the above method– were also marked as deprecated. The only method ofUserPatchAttributes
that was not marked as deprecated is the one that allows setting newuser_metadata
values, as that's the only user attribute that can still be updated from native clients.📎 References
See https://auth0.com/docs/secure/tokens/access-tokens/get-management-api-tokens-for-single-page-applications -> talks about SPAs but also applies to native apps (both are public clients)