Bug #10004
openNot returning a proper error after sending a invalid payload
0%
Description
Description
When sending a invalid payload it should return a 400 bad request error. But currently it return a proper response.
Since the actual payload is faulty the created objects attributes are null.
For returning response it creating a another object as "activity", hence its returning a proper response.
There should be a way to validate the receiving payload.
Also the disabled JMeter test cases should re-enabled after this issue is fixed.
The APIs of device operations need to be modified with the solution.
Ex API : https://repository.entgra.net/proprietary/emm-proprietary-plugins/src/commit/b286f1f4d1f0564fda926a58edc75635dd520850/components/platform-plugins/android-plugin/io.entgra.proprietary.platform.android.api/src/main/java/io/entgra/proprietary/platform/android/api/service/impl/DeviceManagementAdminAPIImpl.java#L1399
Result
Returning a proper response after sending a invalid payload.
Files
Updated by Arshana Atapattu over 1 year ago
In the payload lockcod should be lockcode. but with a faulty payload its giving a response1.
[1]
Updated by Arshana Atapattu over 1 year ago
The JMeter test case: Android Device Management API - Negative Tests
Updated by Viranga Gunarathna over 1 year ago
- Project changed from product-uem 5.3.0 GA to 32