summaryrefslogtreecommitdiffstats
path: root/build/integration/ldap_features
diff options
context:
space:
mode:
authorArthur Schiwon <blizzz@arthur-schiwon.de>2017-01-20 21:57:12 +0100
committerArthur Schiwon <blizzz@arthur-schiwon.de>2017-01-20 22:01:08 +0100
commit9ca4065ef5ccce3a4bc807e4b7bfddd76f50724c (patch)
treeef2094be85ef640cd55b8ac20d3bf933761fa7d3 /build/integration/ldap_features
parent08b31fcb7da9f65e5d4fc87f266a183d1353e193 (diff)
downloadnextcloud-server-9ca4065ef5ccce3a4bc807e4b7bfddd76f50724c.tar.gz
nextcloud-server-9ca4065ef5ccce3a4bc807e4b7bfddd76f50724c.zip
LDAP PUT command now supports setting multiple keys at once
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Diffstat (limited to 'build/integration/ldap_features')
-rw-r--r--build/integration/ldap_features/ldap-ocs.feature28
1 files changed, 17 insertions, 11 deletions
diff --git a/build/integration/ldap_features/ldap-ocs.feature b/build/integration/ldap_features/ldap-ocs.feature
index 2815b308d48..663bdcb56fd 100644
--- a/build/integration/ldap_features/ldap-ocs.feature
+++ b/build/integration/ldap_features/ldap-ocs.feature
@@ -31,28 +31,33 @@ Feature: LDAP
Scenario: Create and modify a configuration
Given As an "admin"
And creating an LDAP configuration at "/apps/user_ldap/api/v1/config"
- When setting "ldapHost" of the LDAP configuration to "ldaps://my.ldap.server"
+ When setting the LDAP configuration to
+ | configData[ldapHost] | ldaps://my.ldap.server |
Then the OCS status code should be "200"
And the HTTP status code should be "200"
- # Testing an invalid config key
- When setting "crack0r" of the LDAP configuration to "foobar"
- Then the OCS status code should be "400"
- And the HTTP status code should be "400"
Scenario: Modifying a non-existing configuration
Given As an "admin"
When sending "PUT" to "/apps/user_ldap/api/v1/config/s666" with
- | key | ldapHost |
- | value | ldaps://my.ldap.server |
+ | configData[ldapHost] | ldaps://my.ldap.server |
Then the OCS status code should be "404"
And the HTTP status code should be "404"
+ Scenario: Modifying an existing configuration with malformed configData
+ Given As an "admin"
+ And creating an LDAP configuration at "/apps/user_ldap/api/v1/config"
+ When setting the LDAP configuration to
+ | configData | ldapHost=ldaps://my.ldap.server |
+ Then the OCS status code should be "400"
+ And the HTTP status code should be "400"
+
Scenario: create, modify and get a configuration
Given As an "admin"
And creating an LDAP configuration at "/apps/user_ldap/api/v1/config"
- And setting "ldapHost" of the LDAP configuration to "ldaps://my.ldap.server"
- And setting "ldapLoginFilter" of the LDAP configuration to "(&(|(objectclass=inetOrgPerson))(uid=%uid))"
- And setting "ldapAgentPassword" of the LDAP configuration to "psst,secret"
+ And setting the LDAP configuration to
+ | configData[ldapHost] | ldaps://my.ldap.server |
+ | configData[ldapLoginFilter] | (&(\|(objectclass=inetOrgPerson))(uid=%uid)) |
+ | configData[ldapAgentPassword] | psst,secret |
When getting the LDAP configuration with showPassword "0"
Then the OCS status code should be "200"
And the HTTP status code should be "200"
@@ -63,7 +68,8 @@ Feature: LDAP
Scenario: receiving password in plain text
Given As an "admin"
And creating an LDAP configuration at "/apps/user_ldap/api/v1/config"
- And setting "ldapAgentPassword" of the LDAP configuration to "psst,secret"
+ And setting the LDAP configuration to
+ | configData[ldapAgentPassword] | psst,secret |
When getting the LDAP configuration with showPassword "1"
Then the OCS status code should be "200"
And the HTTP status code should be "200"