-
Notifications
You must be signed in to change notification settings - Fork 1k
Support PATCH
for identities
#2380
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Using |
PATCH
for identities
Supporting JSON Patch would be useful for updating arrays in an identity. Could it be added too? |
@zepatrik JSON Patch might be a good solution for "merging" traits, as we talked about in #2380. I would even say it might be in scope of the existing PR, and I would be willing to take a look at it over there. There are Golang SDKs available: https://jsonpatch.com/#go WDYT? |
We have PATCH support in Hydra already, we can for sure just copy the approach :) |
Closes #2380 Co-authored-by: aeneasr <[email protected]>
Why I cannot find this PATCH in https://www.ory.sh/docs/kratos/reference/api#operation/adminUpdateIdentity? |
Hope this fixes it: #2784 |
It is not yet released, only merged |
Ok. Sorry. |
Is there no way to patch the identity with HTTP API from frontend at the moment? |
This has long been released |
I mean a use-case when a logged in user patches their own identity. |
Patching Request:
Response:
Request:
Response:
|
An extra example. Request:
Response:
Request:
Response:
|
Request:
Response:
Request:
Response:
|
Similar requests for |
Closes ory#2380 Co-authored-by: aeneasr <[email protected]>
Patching a field in metadata_public works but the identity returned doesn't include the change, metadata_public is null |
Uh oh!
There was an error while loading. Please reload this page.
Preflight checklist
Describe your problem
I think it sholud be possible to use
adminUpdateIdentity
without passing a traits object in it (or anil
).I'm using it only to change state of the identity (active/inactive).
Is there another way?
Version
0.9.0-alpha.3
The text was updated successfully, but these errors were encountered: