Skip to content

Commit

Permalink
fixup! prov api to be able to edit multivalue properties
Browse files Browse the repository at this point in the history
  • Loading branch information
blizzz committed Jun 14, 2021
1 parent 3637af2 commit 085fd99
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions build/integration/features/provisioning-v1.feature
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ Feature: provisioning
And the HTTP status code should be "200"
And sending "PUT" to "/cloud/users/brand-new-user" with
| key | additional_email |
| value | no.reply@nextcloud.com |
| value | my-alias@example.org |
And the OCS status code should be "100"
And the HTTP status code should be "200"
And sending "PUT" to "/cloud/users/brand-new-user" with
Expand Down Expand Up @@ -137,7 +137,7 @@ Feature: provisioning
| id | brand-new-user |
| displayname | Brand New User |
| email | no-reply@nextcloud.com |
| additional_mail | no.reply@nextcloud.com;noreply@nextcloud.com |
| additional_mail | my-alias@example.org;noreply@nextcloud.com |
| phone | +4971125242890 |
| address | Foo Bar Town |
| website | https://nextcloud.com |
Expand Down Expand Up @@ -196,7 +196,7 @@ Feature: provisioning
And As an "brand-new-user"
When sending "PUT" to "/cloud/users/brand-new-user" with
| key | additional_email |
| value | no.reply@nextcloud.com |
| value | my-alias@example.org |
And the OCS status code should be "100"
And the HTTP status code should be "200"
And sending "PUT" to "/cloud/users/brand-new-user" with
Expand All @@ -205,7 +205,7 @@ Feature: provisioning
And the OCS status code should be "100"
And the HTTP status code should be "200"
When sending "PUT" to "/cloud/users/brand-new-user/additional_emailScope" with
| key | no.reply@nextcloud.com |
| key | my-alias@example.org |
| value | v2-federated |
Then the OCS status code should be "100"
And the HTTP status code should be "200"
Expand Down Expand Up @@ -242,11 +242,11 @@ Feature: provisioning
And As an "brand-new-user"
When sending "PUT" to "/cloud/users/brand-new-user" with
| key | additional_email |
| value | no.reply@nextcloud.com |
| value | my-alias@example.org |
And the OCS status code should be "100"
And the HTTP status code should be "200"
When sending "PUT" to "/cloud/users/brand-new-user/additional_emailScope" with
| key | no.reply@nextcloud.com |
| key | my-alias@example.org |
| value | invalid |
Then the OCS status code should be "102"
And the HTTP status code should be "200"
Expand All @@ -256,7 +256,7 @@ Feature: provisioning
And As an "brand-new-user"
When sending "PUT" to "/cloud/users/brand-new-user" with
| key | additional_email |
| value | no.reply@nextcloud.com |
| value | my-alias@example.org |
And the OCS status code should be "100"
And the HTTP status code should be "200"
And sending "PUT" to "/cloud/users/brand-new-user" with
Expand All @@ -265,14 +265,14 @@ Feature: provisioning
And the OCS status code should be "100"
And the HTTP status code should be "200"
When sending "PUT" to "/cloud/users/brand-new-user/additional_email" with
| key | no.reply@nextcloud.com |
| key | my-alias@example.org |
| value | |
And the OCS status code should be "100"
And the HTTP status code should be "200"
Then user "brand-new-user" has
| additional_email | noreply@nextcloud.com |
Then user "brand-new-user" has not
| additional_email | no.reply@nextcloud.com |
| additional_email | my-alias@example.org |

Scenario: An admin cannot edit user account property scopes
Given As an "admin"
Expand Down

0 comments on commit 085fd99

Please sign in to comment.