Repository navigation
Replies: 1 comment
As discussed on #28220 this is the correct expected behavior. There were no plans to implement PATCH or additional endpoints to implement alternative behavior with the current admin api. We are discussing how this will work with our next iteration of the admin api - see #37655 and other disussions / issues about the directions we would like to take. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Keycloak team,
I am encountering a significant issue when updating a single attribute of a user in Keycloak. Currently, in order to update just one attribute (e.g., p24uid), we are required to send the entire user object, including all attributes, even if they haven’t changed. This results in unnecessary overhead, especially when the number of attributes is large.
This behavior is problematic for several reasons:
Unnecessary data handling: Every time we need to update one attribute, we must read and send all user attributes, causing inefficiencies in our system.
Risk of overwriting other attributes: Since we have to send the entire user object, there is a risk of accidentally modifying other attributes that we do not intend to change.
Complexity in multi-use cases: When this operation is needed in multiple places (e.g., in different microservices or API endpoints), it becomes difficult to maintain and prone to errors.
This limitation makes it harder to work efficiently with the Keycloak API in certain scenarios, especially when user attributes are complex or numerous. It would be extremely helpful if there were a more granular way to update specific attributes without sending the entire user object in the request.
Does anyone have a solution or a workaround for this issue? How can we update only one attribute without needing to send all user data?
Thanks in advance for any help or suggestions!
Best regards,
M.D.N
All reactions