diff --git a/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature b/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature
index b320facd5d0e..3e799473868e 100644
--- a/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature
+++ b/tests/acceptance/features/apiProvisioning-v1/resetUserPassword.feature
@@ -72,6 +72,7 @@ Feature: reset user password
     And the content of file "textfile0.txt" for user "brand-new-user" using password "%alt1%" should be "ownCloud test text file 0" plus end-of-line
     But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
 
+  @skipOnEncryptionType:user-keys @encryption-issue-57
   Scenario Outline: reset user password including emoji
     Given these users have been created:
       | username       | password  | displayname | email                    |
@@ -80,10 +81,10 @@ Feature: reset user password
     Then the OCS status code should be "100"
     And the HTTP status code should be "200"
     And the content of file "textfile0.txt" for user "brand-new-user" using password "<password>" should be "ownCloud test text file 0" plus end-of-line
+    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
     Examples:
       | password        | comment  |
       | 😛 😜           | smileys  |
       | 🐶🐱 🐭           | Animals  |
       | ⌚️ 📱 📲 💻           | objects  |
       | 🚴🏿‍♀️ 🚴‍♂️            | cycling |
-    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
\ No newline at end of file
diff --git a/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature b/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature
index 40209b88e575..605087c102ef 100644
--- a/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature
+++ b/tests/acceptance/features/apiProvisioning-v2/resetUserPassword.feature
@@ -72,6 +72,7 @@ Feature: reset user password
     And the content of file "textfile0.txt" for user "brand-new-user" using password "%alt1%" should be "ownCloud test text file 0" plus end-of-line
     But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
 
+  @skipOnEncryptionType:user-keys @encryption-issue-57
   Scenario Outline: reset user password including emoji
     Given these users have been created:
       | username       | password  | displayname | email                    |
@@ -80,10 +81,10 @@ Feature: reset user password
     Then the OCS status code should be "200"
     And the HTTP status code should be "200"
     And the content of file "textfile0.txt" for user "brand-new-user" using password "<password>" should be "ownCloud test text file 0" plus end-of-line
+    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
     Examples:
       | password        | comment  |
       | 😛 😜           | smileys  |
       | 🐶🐱 🐭           | Animals  |
       | ⌚️ 📱 📲 💻           | objects  |
       | 🚴🏿‍♀️ 🚴‍♂️            | cycling |
-    But user "brand-new-user" using password "%regular%" should not be able to download file "textfile0.txt"
\ No newline at end of file