diff --git a/.drone.star b/.drone.star
index 0d3eaf6cb6d3..c8d7072c4b23 100644
--- a/.drone.star
+++ b/.drone.star
@@ -273,6 +273,16 @@ config = {
 			'runAllSuites': True,
 			'numberOfParts': 8,
 		},
+		'apiOnSqlite': {
+			'suites': {
+				'apiOnSqlite': 'apiOnSqlite',
+			},
+			'databases': ['sqlite'],
+			'useHttps': False,
+			'filterTags': '@onSqliteDb',
+			'runAllSuites': True,
+			'numberOfParts': 2,
+		}
 	}
 }
 
diff --git a/tests/acceptance/features/apiProvisioning-v1/addUser.feature b/tests/acceptance/features/apiProvisioning-v1/addUser.feature
index b20095d1697b..a278cc1bf0b5 100644
--- a/tests/acceptance/features/apiProvisioning-v1/addUser.feature
+++ b/tests/acceptance/features/apiProvisioning-v1/addUser.feature
@@ -197,3 +197,20 @@ Feature: add user
     Then the OCS status code should be "105"
     And the HTTP status code should be "200"
     And user "brand-new-user" should not exist
+
+  @onSqliteDb
+  Scenario: admin tries to create user with brackets in the username
+    Given the following users have been deleted
+      | username  |
+      | [user1]   |
+      | [ user2 ] |
+    When the administrator sends a user creation request for the following users with password using the provisioning API
+      | username  | password |
+      | [user1]   | %alt1%   |
+      | [ user2 ] | %alt1%   |
+    Then the OCS status code of responses on all endpoints should be "101"
+    And the HTTP status code of responses on all endpoints should be "200"
+    And the following users should not exist
+      | username  |
+      | [user1]   |
+      | [ user2 ] |
diff --git a/tests/acceptance/features/apiProvisioning-v2/addUser.feature b/tests/acceptance/features/apiProvisioning-v2/addUser.feature
index a735efa34592..463d1f4780a1 100644
--- a/tests/acceptance/features/apiProvisioning-v2/addUser.feature
+++ b/tests/acceptance/features/apiProvisioning-v2/addUser.feature
@@ -197,3 +197,20 @@ Feature: add user
     Then the OCS status code should be "400"
     And the HTTP status code should be "400"
     And user "brand-new-user" should not exist
+
+  @onSqliteDb
+  Scenario: admin tries to create user with brackets in the username
+    Given the following users have been deleted
+      | username  |
+      | [user1]   |
+      | [ user2 ] |
+    When the administrator sends a user creation request for the following users with password using the provisioning API
+      | username  | password |
+      | [user1]   | %alt1%   |
+      | [ user2 ] | %alt1%   |
+    Then the OCS status code of responses on all endpoints should be "400"
+    And the HTTP status code of responses on all endpoints should be "400"
+    And the following users should not exist
+      | username  |
+      | [user1]   |
+      | [ user2 ] |
diff --git a/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature b/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature
index 538980b548a1..5c273e801070 100644
--- a/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature
+++ b/tests/acceptance/features/apiProvisioningGroups-v1/addGroup.feature
@@ -22,20 +22,23 @@ Feature: add groups
       | España§àôœ€ |
       | नेपाली        |
 
+  @onSqliteDb
   Scenario: admin creates a group with special characters
     When the administrator sends a group creation request for the following groups using the provisioning API
-      | groupname           | comment                                 |
-      | brand-new-group     | dash                                    |
-      | the.group           | dot                                     |
-      | left,right          | comma                                   |
-      | 0                   | The "false" group                       |
-      | Finance (NP)        | Space and brackets                      |
-      | Admin&Finance       | Ampersand                               |
-      | admin:Pokhara@Nepal | Colon and @                             |
-      | maint+eng           | Plus sign                               |
-      | $x<=>[y*z^2]!       | Maths symbols                           |
-      | Mgmt\Middle         | Backslash                               |
-      | 😅 😆               | emoji                                   |
+      | groupname           | comment            |
+      | brand-new-group     | dash               |
+      | the.group           | dot                |
+      | left,right          | comma              |
+      | 0                   | The "false" group  |
+      | Finance (NP)        | Space and brackets |
+      | Admin&Finance       | Ampersand          |
+      | admin:Pokhara@Nepal | Colon and @        |
+      | maint+eng           | Plus sign          |
+      | $x<=>[y*z^2]!       | Maths symbols      |
+      | Mgmt\Middle         | Backslash          |
+      | 😅 😆               | emoji              |
+      | [group1]            | brackets           |
+      | group [ 2 ]         | bracketsAndSpace   |
     Then the OCS status code of responses on all endpoints should be "100"
     And the HTTP status code of responses on all endpoints should be "200"
     And these groups should exist:
@@ -51,6 +54,8 @@ Feature: add groups
       | $x<=>[y*z^2]!       |
       | Mgmt\Middle         |
       | 😅 😆               |
+      | [group1]            |
+      | group [ 2 ]         |
 
   @toImplementOnOCIS @issue-product-284
   Scenario: admin creates a group with % and # in name