From f93db724d7905d9858af2d2d4cf083c20b9c28de Mon Sep 17 00:00:00 2001 From: Lukas Reschke Date: Thu, 18 May 2017 21:19:39 +0200 Subject: Make legacy DAV backend use the BearerAuth backend as well Signed-off-by: Lukas Reschke --- build/integration/features/auth.feature | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'build') diff --git a/build/integration/features/auth.feature b/build/integration/features/auth.feature index edcca4bcd4e..679b2465659 100644 --- a/build/integration/features/auth.feature +++ b/build/integration/features/auth.feature @@ -53,10 +53,14 @@ Feature: auth When requesting "/remote.php/webdav" with "PROPFIND" using restricted basic token auth Then the HTTP status code should be "207" - Scenario: using WebDAV with restricted basic token auth + Scenario: using old WebDAV endpoint with unrestricted client token When requesting "/remote.php/webdav" with "PROPFIND" using an unrestricted client token Then the HTTP status code should be "207" + Scenario: using new WebDAV endpoint with unrestricted client token + When requesting "/remote.php/dav/" with "PROPFIND" using an unrestricted client token + Then the HTTP status code should be "207" + Scenario: using WebDAV with browser session Given a new browser session is started When requesting "/remote.php/webdav" with "PROPFIND" using browser session -- cgit v1.2.3