Skip to content
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

User facet in Sharing Permission has invalid user Id (OneDrive Personal) #2832

Open
23W opened this issue Feb 13, 2025 · 1 comment
Open
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience

Comments

@23W
Copy link

23W commented Feb 13, 2025

Describe the bug

The file was shared from one Personal account to other Personal account with "edit" right (Role is writer). If MsGraph is signed in as delegated by this other Personal account and executes await graphClient.Drives["{drive-id}"].Items["{driveItem-id}"].Permissions.GetAsync() to get the item permissions it will receive collection of permissions for file owner and for this account.

The permission for this account will have filed grantedToIdentities with user facet (see https://learn.microsoft.com/en-us/graph/api/resources/permission?view=graph-rest-1.0#properties and https://learn.microsoft.com/en-us/graph/api/resources/identityset?view=graph-rest-1.0#properties).

User face will have correct user's displayName but wrong id.

Example:
Image

The correct user id for this delegated account you can see by await graphClient.Me.Request().GetAsycn().
This is not "46" but "5f6aae90c74bde86".

Image

Expected behavior

User facet should have correct user's id.

How to reproduce

execute get list of shared with me file permissions and compare user's id with id of the same account but get from me request.

SDK Version

4.11.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@23W 23W added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Feb 13, 2025
@23W
Copy link
Author

23W commented Feb 13, 2025

this is new bug, around month ago everything worked fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

1 participant