auth.feature 2.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778
  1. Feature: auth
  2. Background:
  3. Given user "user0" exists
  4. Given a new client token is used
  5. # FILES APP
  6. Scenario: access files app anonymously
  7. When requesting "/index.php/apps/files" with "GET"
  8. Then the HTTP status code should be "401"
  9. Scenario: access files app with basic auth
  10. When requesting "/index.php/apps/files" with "GET" using basic auth
  11. Then the HTTP status code should be "200"
  12. Scenario: access files app with basic token auth
  13. When requesting "/index.php/apps/files" with "GET" using basic token auth
  14. Then the HTTP status code should be "200"
  15. Scenario: access files app with a client token
  16. When requesting "/index.php/apps/files" with "GET" using a client token
  17. Then the HTTP status code should be "200"
  18. Scenario: access files app with browser session
  19. Given a new browser session is started
  20. When requesting "/index.php/apps/files" with "GET" using browser session
  21. Then the HTTP status code should be "200"
  22. # WebDAV
  23. Scenario: using WebDAV anonymously
  24. When requesting "/remote.php/webdav" with "PROPFIND"
  25. Then the HTTP status code should be "401"
  26. Scenario: using WebDAV with basic auth
  27. When requesting "/remote.php/webdav" with "PROPFIND" using basic auth
  28. Then the HTTP status code should be "207"
  29. Scenario: using WebDAV with token auth
  30. When requesting "/remote.php/webdav" with "PROPFIND" using basic token auth
  31. Then the HTTP status code should be "207"
  32. # DAV token auth is not possible yet
  33. #Scenario: using WebDAV with a client token
  34. # When requesting "/remote.php/webdav" with "PROPFIND" using a client token
  35. # Then the HTTP status code should be "207"
  36. Scenario: using WebDAV with browser session
  37. Given a new browser session is started
  38. When requesting "/remote.php/webdav" with "PROPFIND" using browser session
  39. Then the HTTP status code should be "207"
  40. # OCS
  41. Scenario: using OCS anonymously
  42. When requesting "/ocs/v1.php/apps/files_sharing/api/v1/remote_shares" with "GET"
  43. Then the OCS status code should be "997"
  44. Scenario: using OCS with basic auth
  45. When requesting "/ocs/v1.php/apps/files_sharing/api/v1/remote_shares" with "GET" using basic auth
  46. Then the OCS status code should be "100"
  47. Scenario: using OCS with token auth
  48. When requesting "/ocs/v1.php/apps/files_sharing/api/v1/remote_shares" with "GET" using basic token auth
  49. Then the OCS status code should be "100"
  50. Scenario: using OCS with client token
  51. When requesting "/ocs/v1.php/apps/files_sharing/api/v1/remote_shares" with "GET" using a client token
  52. Then the OCS status code should be "100"
  53. Scenario: using OCS with browser session
  54. Given a new browser session is started
  55. When requesting "/ocs/v1.php/apps/files_sharing/api/v1/remote_shares" with "GET" using browser session
  56. Then the OCS status code should be "100"