diff --git a/code/Test_definitions/geofencing-subscriptions-createGeofencingSubscription.feature b/code/Test_definitions/geofencing-subscriptions-createGeofencingSubscription.feature
index 4e1cde9d..dec89013 100644
--- a/code/Test_definitions/geofencing-subscriptions-createGeofencingSubscription.feature
+++ b/code/Test_definitions/geofencing-subscriptions-createGeofencingSubscription.feature
@@ -237,19 +237,6 @@ Feature: Camara Geofencing Subscriptions API, vwip - Operation createGeofencingS
     And the response property "$.code" is "SERVICE_NOT_APPLICABLE"
     And the response property "$.message" contains a user-friendly text
 
- # Several identifiers provided but they do not identify the same device
- # This scenario may happen with 2-legged access tokens, which do not identify a device
-  @geofencing_subscriptions_C01.08_device_identifiers_mismatch
-  Scenario: Device identifiers mismatch
-    Given the header "Authorization" is set to a valid access token which does not identify a single device
-    And at least 2 types of device identifiers are supported by the implementation
-    And the request body property "$.config.subscriptionDetail.device" includes several identifiers, each of them identifying a valid but different device
-    When the request "createGeofencingSubscription" is sent
-    Then the response status code is 422
-    And the response property "$.status" is 422
-    And the response property "$.code" is "IDENTIFIER_MISMATCH"
-    And the response property "$.message" contains a user friendly text
-
   # Error code 400
 
   @geofencing_subscriptions_400.1_create_subscriptions_with_invalid_parameter
diff --git a/code/Test_definitions/location-retrieval.feature b/code/Test_definitions/location-retrieval.feature
index 337ed807..4e67d7bf 100644
--- a/code/Test_definitions/location-retrieval.feature
+++ b/code/Test_definitions/location-retrieval.feature
@@ -156,19 +156,6 @@ Feature: CAMARA Device location retrieval API, vwip - Operation retrieveLocation
     And the response property "$.code" is "SERVICE_NOT_APPLICABLE"
     And the response property "$.message" contains a user-friendly text
 
-  # Several identifiers provided but they do not identify the same device
-  # This scenario may happen with 2-legged access tokens, which do not identify a device
-  @location_retrieval_C01.08_device_identifiers_mismatch
-  Scenario: Device identifiers mismatch
-    Given the header "Authorization" is set to a valid access token which does not identify a single device
-    And at least 2 types of device identifiers are supported by the implementation
-    And the request body property "$.device" includes several identifiers, each of them identifying a valid but different device
-    When the request "retrieveLocation" is sent
-    Then the response status code is 422
-    And the response property "$.status" is 422
-    And the response property "$.code" is "IDENTIFIER_MISMATCH"
-    And the response property "$.message" contains a user friendly text
-
   # Error code 400
 
   @location_retrieval_400.1_no_request_body