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.

Sign up for GitHub

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

Jump to bottom

[tests-only][full-ci] Added test to reshare a resource to other users with higher roles #8147

Merged
merged 1 commit into from
Jan 25, 2024
Merged

[tests-only][full-ci] Added test to reshare a resource to other users with higher roles #8147

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
106 changes: 106 additions & 0 deletions tests/acceptance/features/apiSharingNg/reshare.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,3 +123,109 @@ Feature: Reshare a share invitation
| Editor | Viewer |
| Editor | Editor |
| Editor | Uploader |


Scenario: try to reshare a resource to higher roles
Given user "Alice" has uploaded file with content "to share" to "/textfile1.txt"
And user "Alice" has sent the following share invitation:
| resourceType | file |
| resource | textfile1.txt |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Viewer |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | file |
| resource | textfile1.txt |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | File Editor |
Then the HTTP status code should be "403"
And the JSON data of the response should match
"""
{
"type": "object",
"required": [
"error"
],
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "string",
"enum": [
"accessDenied"
]
},
"message": {
"type": "string",
"enum": [
"insufficient permissions to create that kind of share"
]
}
}
}
}
}
"""
And for user "Carol" the space Shares should not contain these entries:
| textfile1.txt |


Scenario: user with role Uploader tries to reshare a folder
Given user "Alice" has created folder "FolderToShare"
And user "Alice" has sent the following share invitation:
| resourceType | folder |
| resource | FolderToShare |
| space | Personal |
| sharee | Brian |
| shareType | user |
| permissionsRole | Uploader |
When user "Brian" sends the following share invitation using the Graph API:
| resourceType | folder |
| resource | FolderToShare |
| space | Shares |
| sharee | Carol |
| shareType | user |
| permissionsRole | Viewer |
Then the HTTP status code should be "403"
And the JSON data of the response should match
"""
{
"type": "object",
"required": [
"error"
],
"properties": {
"error": {
"type": "object",
"required": [
"code",
"message"
],
"properties": {
"code": {
"type": "string",
"enum": [
"accessDenied"
]
},
"message": {
"type": "string",
"enum": [
"no permission to add grants on shared resource"
]
}
}
}
}
}
"""
And for user "Carol" the space Shares should not contain these entries:
| textfile1.txt |