Description
Currently, the custome user claims can be updated with setCustomUserClaims()
, and the user details can be updated with updateUser()
.
Both use same /accounts:update
REST API under the hood.
Is there a particular reason why the updateUser()
method does not allow updating the custom claims even though it is possible in the underlying REST API? A follow up point is: if the updateUser()
method has this functionalitly, then the setCustomUserClaims()
would become obsolete (just a convenience wrapper).
I'd like to be able to include a customClaims
field in the UpdateRequest
interface, so that, if needed, we can update the user's details and claims in a single request. Currently we need two separate network requests to do this.
Let me know, and I can help with a PR if you want.
Activity
google-oss-bot commentedon Aug 18, 2022
I found a few problems with this issue:
brettwillis commentedon Aug 22, 2022
Side question: There seems to be a very low request rate quota on this
/accounts:update
API. I can't find it explicitly stated but it feels like 10 req/second, as per the account delete rate quota. Can you confirm what the quota is for this API?This only makes it more important to be able to combine requests.