-
Notifications
You must be signed in to change notification settings - Fork 187
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
Improve users/groups graph api endpoint #3837
Comments
FYI @butonic Please NOTE: The API specification claims that point 1-4 is already possible, which is not the case. We SHOULD really not add things to our API specification which are not included yet, the specification should represent the current state AND NOT contain future improvements |
let us treat it as a bug and fix it. |
@janackermann && @micbar 5 & 6 are not part of the spec (see https://docs.microsoft.com/en-us/graph/api/resources/user?view=graph-rest-1.0#relationships) do we want to implement outside of the spec? |
i would say skip 5 & 6 for now, i'm really not happy to work around the spec atm. |
I agree, 5 & 6 can be mitigated client side for the moment. 1-4 would be good to have. |
@dragonchaser, point 5 & 6 is extracted into a separate issue to keep this rolling. |
To build up a performant user management with user and group assignments it is necessary to improve the graph API:
/graph/v1.0/users/
endpoint should include a field where assigned groups are listed (maybe $expand is necessary)/graph/v1.0/users/{id}/
endpoint should include a field where assigned groups are listed (maybe $expand is necessary)/graph/v1.0/groups/
endpoint should include a field where assigned users are listed (maybe $expand is necessary)/graph/v1.0/groups/{id}/
endpoint should include a field where users are listed (maybe $expand is necessary)We need an endpoint to set the user's group with one request instead of adding and deleting group relations by single requestsWe need an endpoint to set the group's users with one request instead of adding and deleting user relations by single requests5 & 6 extracted into it's own issue
The text was updated successfully, but these errors were encountered: