enhancement: make use of unified role for the graph invitation endpoint

[fschade]

Description

Up to now the graph beta invitation endpoint made use of the cs3 permission objects (named set aka role).
With the implementation of the new unified roles the api is now able to use those as described in the swagger spec.

Related Issue

• enhancement: add graph beta sharedWithMe API #7633
• Make v1beta1/roleManagement/permissions/roleDefinitions/ beta #7686
• Fix url path for getsharedbyme #7684
• graph: reuse user- and group cache in graph/sharedbyme #7683
• Initial implementation of /me/drives/sharedByMe endpoint #7239
• [full-ci] Enhancement(sharing-ng): add invitation graph beta api #7687
• enhancement: make use of unified role for the graph invitation endpoint #7751
• add Sharing NG endpoints libre-graph-api#112
• [ocis] implement /me/drives/sharedWithMe #7436
• Sharing NG #6993

Motivation and Context

make use of the unified roles as described in the openAPI spec.

How Has This Been Tested?

• manual testing
• unit tests

example:

request

POST {{host}}/graph/v1beta1/drives/{{drive-id}}/items/{{item-id}}/invite
Authorization: Basic {{user_admin_login}} {{user_admin_password}}
Content-Type: application/json

body (roles)

{
  "recipients":[
    {"objectId": "{{user_marie_id}}"}
  ],
  "ExpirationDateTime": "2055-07-15T14:00:00.000Z",
  "roles": [
    "{{role_viewer_id}}",
  ]
}

response (roles)

{
  "value": [
    {
      "expirationDateTime": "2055-07-15T16:00:00+02:00",
      "grantedToV2": {
        "user": {
          "displayName": "Marie Skłodowska Curie",
          "id": "f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"
        }
      },
      "id": "3496f80c-b4c7-40cd-9ee9-f7bfb77c671c:4353a0e1-a947-4588-8be2-7730ac879eda:592a5934-9dda-41f9-8925-ae96411dbdb8",
      "roles": [
        "b1e2218d-eef8-4d4c-b82d-0f1a1b48f3b5"
      ]
    }
  ]
}

body (@libre.graph.permissions.actions)

{
  "recipients":[
    {"objectId": "{{user_marie_id}}"}
  ],
  "ExpirationDateTime": "2055-07-15T14:00:00.000Z",
  "@libre.graph.permissions.actions":[
    "libre.graph/driveItem/content/read"
  ]
}

response (@libre.graph.permissions.actions)

{
  "value": [
    {
      "@libre.graph.permissions.actions": [
        "libre.graph/driveItem/content/read"
      ],
      "expirationDateTime": "2055-07-15T16:00:00+02:00",
      "grantedToV2": {
        "user": {
          "displayName": "Marie Skłodowska Curie",
          "id": "f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c"
        }
      },
      "id": "3496f80c-b4c7-40cd-9ee9-f7bfb77c671c:4353a0e1-a947-4588-8be2-7730ac879eda:53cff278-5c94-47b1-99ca-5ce89095b385"
    }
  ]
}

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

98.7% Coverage
0.0% Duplication