User is not getting updated on v2
He Team,
With the recent change : https://github.com/zitadel/zitadel/pull/8635
The user details are not getting updated, I am on version 2.62 and on passing the user details in body, the response is 200, although the user details are not updated.
PUT: http://custom_domain/v2/users/human/:userId
Request Body:
Respone:
The user details are not updated
GitHub
fix: use body for update user on user v2 API by stebenz · Pull Requ...
Use body for update user endpoint on user v2 API.
21 Replies
Which version of 2.62 are you using?
only 2.62.3 contains the patch of above PR
nevermind...Bumped up the version to 2.62.3
just to understand for the previous version, where is the documentation to refere to?
what docs are you looking for exactly?
To update the user info...for the older versions how would I be able to do that?
what do you mean by "older version"?
that api had a bug so there is no new version 😄
https://zitadel.com/docs/apis/resources/user_service_v2/user-service-update-human-user
https://zitadel.com/docs/apis/resources/user_service_v2/user-service-update-human-user
earlier we were using
PUT:
/v2beta/users/${userId}?${params}
passing evrything as params.... so upto v2.62.2 this is the only way to do?
no, that pr actually brought that you can use a body (which we use as default)
my concern is on v 2.62.2,
what should be the API that will work?
I do not understand your question, sorry.
The api is exactly the same just the body was not working.
the one from the doc is:
https://$CUSTOM-DOMAIN/v2/users/human/:userId
and the one we were using earlier was:
https://$CUSTOM-DOMAIN/v2beta/users/:userId?{params}
where there was no body and the details were passed as query params to be updated.
I want to understand that below v 2.62.3 , I have to follow this way of passing data as query params?
because https://$CUSTOM-DOMAIN/v2/users/human/:userId only works with 2.62.3
You should still be able to use param in 2.62.3 @stebenz correct me if I am wrong.
The beta api graduated into a stable api recently but the design should be the same.
Unfourtunately, it does not work...it gives 405
{
"code": 12,
"message": "Method Not Allowed"
}
Unknown User•12mo ago
Message Not Public
Sign In & Join Server To View
yes, that correct
out of curiosity what method do you use?
PUT
well, yeah that should not bring upt that error 😂
so now I am only left with option to use /v2beta if I do not upgrade ?
if you do not upgrade zitadel or your code?
Both actually😅
If i do not upgrade zitadel then I won’t be able to use the existing code and If I update the code , I won’t need able to use existing zitadel version 😅
so I would upgrade zitadel 😄