mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-01-02 18:30:14 -06:00
3cea035d6d
* test(api): use new json schema assertion lib that supports latest schema drafts * test(api): fix json schema * test(api): fix method call * test(api): update expected failure lines * test(api): add custom schema validator * test(api): add custom schema validator * test(api): add custom schema validator * test(api): add custom schema validator * test(api): make json array validation strict * test(api): fix php code style * test(api): update expected failure lines
1644 lines
44 KiB
Gherkin
1644 lines
44 KiB
Gherkin
Feature: get users
|
|
As an admin
|
|
I want to be able to retrieve user information
|
|
So that I can see the information
|
|
|
|
Background:
|
|
Given these users have been created with default attributes and without skeleton files:
|
|
| username |
|
|
| Alice |
|
|
| Brian |
|
|
|
|
|
|
Scenario: admin user gets the information of a user
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
When user "Alice" gets information of user "Brian" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
@issue-5125
|
|
Scenario Outline: non-admin user tries to get the information of a user
|
|
Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
|
|
And the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
|
|
When user "Brian" tries to get information of user "Alice" using Graph API
|
|
Then the HTTP status code should be "401"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message":{
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole | role |
|
|
| Space Admin | Space Admin |
|
|
| Space Admin | User |
|
|
| Space Admin | User Light |
|
|
| Space Admin | Admin |
|
|
| User | Space Admin |
|
|
| User | User |
|
|
| User | User Light |
|
|
| User | Admin |
|
|
| User Light | Space Admin |
|
|
| User Light | User |
|
|
| User Light | User Light |
|
|
| User Light | Admin |
|
|
|
|
|
|
Scenario: admin user gets all users
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
When user "Alice" gets all users using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the user "Alice Hansen" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should contain the user "Brian Murphy" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario: admin user gets all users include disabled users
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And the user "Alice" has disabled user "Brian"
|
|
When user "Alice" gets all users using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the user "Alice Hansen" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should contain the user "Brian Murphy" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [false]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario Outline: non-admin user tries to get all users
|
|
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
|
|
When user "Brian" tries to get all users using the Graph API
|
|
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": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["search term too short"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets the drive information of a user
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
When the user "Alice" gets user "Brian" along with his drive information using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"drive",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
},
|
|
"drive": {
|
|
"type": "object",
|
|
"required": [
|
|
"driveAlias",
|
|
"id",
|
|
"name",
|
|
"owner",
|
|
"quota",
|
|
"root",
|
|
"webUrl"
|
|
],
|
|
"properties": {
|
|
"driveType" : {
|
|
"type": "string",
|
|
"enum": ["personal"]
|
|
},
|
|
"driveAlias" : {
|
|
"type": "string",
|
|
"enum": ["personal/brian"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%space_id_pattern%$"
|
|
},
|
|
"name": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"owner": {
|
|
"type": "object",
|
|
"required": [
|
|
"user"
|
|
],
|
|
"properties": {
|
|
"user": {
|
|
"type": "object",
|
|
"required": [
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "%user_id_pattern%"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"quota": {
|
|
"type": "object",
|
|
"required": [
|
|
"state"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
}
|
|
}
|
|
},
|
|
"root": {
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"webDavUrl"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
},
|
|
"webDavUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/dav/spaces/%space_id_pattern%$"
|
|
}
|
|
}
|
|
},
|
|
"webUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/f/%space_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario Outline: user gets his/her own information along with drive information
|
|
Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
|
|
When the user "Brian" gets his drive information using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"drive",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
},
|
|
"drive": {
|
|
"type": "object",
|
|
"required": [
|
|
"driveAlias",
|
|
"id",
|
|
"name",
|
|
"owner",
|
|
"quota",
|
|
"root",
|
|
"webUrl"
|
|
],
|
|
"properties": {
|
|
"driveType" : {
|
|
"type": "string",
|
|
"enum": ["personal"]
|
|
},
|
|
"driveAlias" : {
|
|
"type": "string",
|
|
"enum": ["personal/brian"]
|
|
},
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%space_id_pattern%$"
|
|
},
|
|
"name": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"owner": {
|
|
"type": "object",
|
|
"required": [
|
|
"user"
|
|
],
|
|
"properties": {
|
|
"user": {
|
|
"type": "object",
|
|
"required": [
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "%user_id_pattern%"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"quota": {
|
|
"type": "object",
|
|
"required": [
|
|
"state"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
}
|
|
}
|
|
},
|
|
"root": {
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"webDavUrl"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
},
|
|
"webDavUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/dav/spaces/%space_id_pattern%$"
|
|
}
|
|
}
|
|
},
|
|
"webUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/f/%space_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole |
|
|
| Admin |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets the group information of a user
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And user "Brian" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
When the user "Alice" gets user "Brian" along with his group information using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"memberOf": {
|
|
"type": "array",
|
|
"minItems": 2,
|
|
"maxItems": 2,
|
|
"uniqueItems": true,
|
|
"items": {
|
|
"oneOf": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["tea-lover"]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["coffee-lover"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
@issue-5125
|
|
Scenario Outline: non-admin user tries to get the group information of a user
|
|
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
|
|
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
|
|
And group "coffee-lover" has been created
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
When the user "Alice" gets user "Brian" along with his group information using Graph API
|
|
Then the HTTP status code should be "401"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message: {
|
|
"type": "string",
|
|
"enum": ["Unauthorized"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole | role |
|
|
| Space Admin | Space Admin |
|
|
| Space Admin | User |
|
|
| Space Admin | User Light |
|
|
| Space Admin | Admin |
|
|
| User | Space Admin |
|
|
| User | User |
|
|
| User | User Light |
|
|
| User | Admin |
|
|
| User Light | Space Admin |
|
|
| User Light | User |
|
|
| User Light | User Light |
|
|
| User Light | Admin |
|
|
|
|
|
|
Scenario: admin user gets all users of certain groups
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And user "Carol" has been created with default attributes and without skeleton files
|
|
And the user "Alice" has disabled user "Carol"
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
When the user "Alice" gets all users of the group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 2,
|
|
"maxItems": 2,
|
|
"uniqueItems": true,
|
|
"items": {
|
|
"oneOf": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
|
When the user "Alice" gets all users of two groups "tea-lover,coffee-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 1,
|
|
"maxItems": 1,
|
|
"items": {
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
|
And the JSON data of the response should not contain the user "Alice Hansen" in the item 'value'
|
|
|
|
|
|
Scenario: admin user gets all users of two groups
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And user "Carol" has been created with default attributes and without skeleton files
|
|
And group "tea-lover" has been created
|
|
And group "coffee-lover" has been created
|
|
And group "wine-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
And user "Brian" has been added to group "coffee-lover"
|
|
And user "Carol" has been added to group "wine-lover"
|
|
When the user "Alice" gets all users that are members in the group "tea-lover" or the group "coffee-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the user "Alice Hansen" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Alice"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should contain the user "Brian Murphy" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
But the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
|
|
|
|
|
Scenario Outline: non admin user tries to get users of certain groups
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
|
|
And group "tea-lover" has been created
|
|
And user "Alice" has been added to group "tea-lover"
|
|
When the user "Brian" gets all users of the group "tea-lover" using the Graph API
|
|
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": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["search term too short"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| role |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: admin user gets all users with certain roles and members of a certain group
|
|
Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
|
|
And user "Carol" has been created with default attributes and without skeleton files
|
|
And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API
|
|
And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API
|
|
And group "tea-lover" has been created
|
|
And user "Brian" has been added to group "tea-lover"
|
|
When the user "Alice" gets all users with role "Space Admin" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the user "Brian Murphy" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
And the JSON data of the response should contain the user "Carol King" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["carol@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Carol"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
But the JSON data of the response should not contain the user "Alice Hansen" in the item 'value'
|
|
When the user "Alice" gets all users with role "Space Admin" and member of the group "tea-lover" using the Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should contain the user "Brian Murphy" in the item 'value', the user-details should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"id",
|
|
"mail",
|
|
"onPremisesSamAccountName",
|
|
"accountEnabled",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"id" : {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["brian@example.org"]
|
|
},
|
|
"onPremisesSamAccountName": {
|
|
"type": "string",
|
|
"enum": ["Brian"]
|
|
},
|
|
"accountEnabled": {
|
|
"type": "boolean",
|
|
"enum": [true]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
But the JSON data of the response should not contain the user "Carol King" in the item 'value'
|
|
|
|
|
|
Scenario Outline: non-admin user tries to get users with a certain role
|
|
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
|
|
When the user "Alice" gets all users with role "<role>" using the Graph API
|
|
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": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["search term too short"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole | role |
|
|
| Space Admin | Space Admin |
|
|
| Space Admin | User |
|
|
| Space Admin | User Light |
|
|
| Space Admin | Admin |
|
|
| User | Space Admin |
|
|
| User | User |
|
|
| User | User Light |
|
|
| User | Admin |
|
|
| User Light | Space Admin |
|
|
| User Light | User |
|
|
| User Light | User Light |
|
|
| User Light | Admin |
|
|
|
|
@issue-6017
|
|
Scenario Outline: admin user gets the drive information of a user with different user role
|
|
Given the administrator has assigned the role "<user-role-1>" to user "Alice" using the Graph API
|
|
And the administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
|
|
And user "Brian" has created folder "my_data"
|
|
When user "Alice" gets the personal drive information of user "Brian" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"driveAlias",
|
|
"driveType",
|
|
"id",
|
|
"name",
|
|
"webUrl",
|
|
"owner",
|
|
"quota",
|
|
"root"
|
|
],
|
|
"properties": {
|
|
"driveAlias": {
|
|
"type": "string",
|
|
"enum": ["personal/brian"]
|
|
},
|
|
"driveType": {
|
|
"type": "string",
|
|
"enum": ["personal"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%space_id_pattern%$"
|
|
},
|
|
"name": {
|
|
"type": "string",
|
|
"enum": ["Brian Murphy"]
|
|
},
|
|
"webUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/f/%space_id_pattern%$"
|
|
},
|
|
"owner": {
|
|
"type": "object",
|
|
"required": [
|
|
"user"
|
|
],
|
|
"properties": {
|
|
"user": {
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": [""]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"qouta": {
|
|
"type": "object",
|
|
"required": [
|
|
"state"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
}
|
|
}
|
|
},
|
|
"root": {
|
|
"type": "object",
|
|
"required": [
|
|
"webDavUrl"
|
|
],
|
|
"properties": {
|
|
"webDavUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/dav/spaces/%space_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| user-role-1 | user-role-2 |
|
|
| Admin | Admin |
|
|
| Admin | Space Admin |
|
|
| Admin | User |
|
|
| Admin | User Light |
|
|
| Space Admin | Admin |
|
|
| Space Admin | Space Admin |
|
|
| Space Admin | User |
|
|
| Space Admin | User Light |
|
|
|
|
|
|
Scenario Outline: non-admin user tries to get drive information of other user with different user role
|
|
Given the administrator has assigned the role "<user-role-1>" to user "Alice" using the Graph API
|
|
And the administrator has assigned the role "<user-role-2>" to user "Brian" using the Graph API
|
|
When user "Alice" gets the personal drive information of user "Brian" using Graph API
|
|
Then the HTTP status code should be "404"
|
|
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": ["itemNotFound"]
|
|
},
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["no drive returned from storage"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| user-role-1 | user-role-2 |
|
|
| User | Admin |
|
|
| User | Space Admin |
|
|
| User | User |
|
|
| User | User Light |
|
|
| User Light | Admin |
|
|
| User Light | Space Admin |
|
|
| User Light | User |
|
|
| User Light | User Light |
|
|
|
|
|
|
Scenario Outline: user with different user role gets his/her own drive information
|
|
Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
|
|
When user "Alice" gets own personal drive information using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"driveAlias",
|
|
"driveType",
|
|
"id",
|
|
"name",
|
|
"webUrl",
|
|
"owner",
|
|
"quota",
|
|
"root"
|
|
],
|
|
"properties": {
|
|
"driveAlias": {
|
|
"type": "string",
|
|
"enum": ["personal/alice"]
|
|
},
|
|
"driveType": {
|
|
"type": "string",
|
|
"enum": ["personal"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%space_id_pattern%$"
|
|
},
|
|
"name": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"webUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/f/%space_id_pattern%$"
|
|
},
|
|
"owner": {
|
|
"type": "object",
|
|
"required": [
|
|
"user"
|
|
],
|
|
"properties": {
|
|
"user": {
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": [""]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
},
|
|
"qouta": {
|
|
"type": "object",
|
|
"required": [
|
|
"state"
|
|
],
|
|
"properties": {
|
|
"state": {
|
|
"type": "string",
|
|
"enum": ["normal"]
|
|
}
|
|
}
|
|
},
|
|
"root": {
|
|
"type": "object",
|
|
"required": [
|
|
"webDavUrl"
|
|
],
|
|
"properties": {
|
|
"webDavUrl": {
|
|
"type": "string",
|
|
"pattern": "^%base_url%/dav/spaces/%space_id_pattern%$"
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| userRole |
|
|
| Admin |
|
|
| Space Admin |
|
|
| User |
|
|
| User Light |
|
|
|
|
|
|
Scenario: non-admin user searches other users by display name
|
|
When user "Brian" searches for user "ali" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 1,
|
|
"maxItems": 1,
|
|
"items": {
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario: non-admin user tries to search for a user by display name with less than 3 characters
|
|
When user "Brian" tries to search for user "al" using Graph API
|
|
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": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["search term too short"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
@issue-7990
|
|
Scenario Outline: non-admin user tries to search for a user by display name with invalid characters/token
|
|
Given user "<user>" has been created with default attributes and without skeleton files
|
|
When user "Brian" tries to search for user "<user>" using Graph API
|
|
Then the HTTP status code should be "400"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"error"
|
|
],
|
|
"properties": {
|
|
"error": {
|
|
"type": "object",
|
|
"required": [
|
|
"message"
|
|
],
|
|
"properties": {
|
|
"message": {
|
|
"type": "string",
|
|
"enum": ["Token '<errorToken>' is invalid"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
Examples:
|
|
| user | errorToken |
|
|
| Alice-From-Wonderland | -From-Wonderland |
|
|
| Alice@From@Wonderland | @From@Wonderland |
|
|
|
|
@issue-7990
|
|
Scenario: non-admin user searches other users by e-mail
|
|
When user "Brian" searches for user "%22alice@example.org%22" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 1,
|
|
"maxItems": 1,
|
|
"items": {
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario: non-admin user searches for a disabled users
|
|
Given the user "Admin" has disabled user "Alice"
|
|
When user "Brian" searches for user "alice" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 1,
|
|
"maxItems": 1,
|
|
"items": {
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|
|
|
|
|
|
Scenario: non-admin user searches for multiple users having same displayname
|
|
Given the user "Admin" has created a new user with the following attributes:
|
|
| userName | another-alice |
|
|
| displayName | Alice Hansen |
|
|
| email | another-alice@example.org |
|
|
| password | containsCharacters(*:!;_+-&) |
|
|
|
|
When user "Brian" searches for user "alice" using Graph API
|
|
Then the HTTP status code should be "200"
|
|
And the JSON data of the response should match
|
|
"""
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"value"
|
|
],
|
|
"properties": {
|
|
"value": {
|
|
"type": "array",
|
|
"minItems": 2,
|
|
"maxItems": 2,
|
|
"uniqueItems": true,
|
|
"items": {
|
|
"oneOf": [
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["alice@example.org"]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "object",
|
|
"required": [
|
|
"displayName",
|
|
"id",
|
|
"mail",
|
|
"userType"
|
|
],
|
|
"properties": {
|
|
"displayName": {
|
|
"type": "string",
|
|
"enum": ["Alice Hansen"]
|
|
},
|
|
"id": {
|
|
"type": "string",
|
|
"pattern": "^%user_id_pattern%$"
|
|
},
|
|
"mail": {
|
|
"type": "string",
|
|
"enum": ["another-alice@example.org"]
|
|
},
|
|
"userType": {
|
|
"type": "string",
|
|
"enum": ["Member"]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
}
|
|
}
|
|
}
|
|
}
|
|
"""
|