Repository navigation
Replies: 1 comment 5 replies
|
IMHO this would be very artificial feature to have it only here. If I would rather like to have something like a bulk API which supports any kind of generic dependencies between objects which can than be used to flatten the calls in the internal API or something like that. e.g. May I miss the point but actually the capabilities to import complex trees as a one off operations is sometimes a problem with keycloak for all domain objects not only for groups. |
|
With my use case I've only encountered the need for this with groups but I'd be happy with a more general solution. |
|
I agree with the use case. And may the Keycloak team also agrees to have it only here. From my perspective its just the feeling this is´a bit artificial. Like, why can i add only one hierarchy here not a tree with more depth etc. |
|
Also is this one way? Or will I always get all children of a group if i request a group? And if not why? |
|
The current behaviour is to return the subgroups from the get endpoints: This is why I initially assumed passing subgroups to the POST endpoint would result in them getting created. |
|
wait what? I didn't know that. If that's the case I wonder why that is. Interesting. |
Uh oh!
There was an error while loading. Please reload this page.
Currently if you wish to create a group with a subgroup this has to be done in two separate calls:
If you provide subgroups to the first call they get ignored and only the top level group is created. It would be nice if endpoint could be used to create nested groups in a single call by providing json similar to this:
{ "name": "parent", "subGroups": [ { "name": "child" } ] }All reactions