The PSE fails to correctly parse requests. For instance, the following request
{"requirement":{"id":"encryption_AES128","description":"Encryption AES 128","type":"TransportEncryption","properties":{"protocol":{"unit":"enum","value":"TLS"},"algorithm":{"unit":"list","value":["TLS_AES_256_GCM_SHA384","TLS_AES_128_GCM_SHA256","TLS_AES_128_CCM_8_SHA256","TLS_AES_128_CCM_SHA256"]},"keyLength":{"unit":"number","value":128}}},"blueprintAttributes":[{"id":"encryption_AES128","description":"Encryption AES 128","type":"TransportEncryption","properties":{"protocol":{"unit":"enum","value":"TLS"},"algorithm":{"unit":"list","value":["TLS_AES_256_GCM_SHA384","TLS_AES_128_GCM_SHA256","TLS_AES_128_CCM_8_SHA256","TLS_AES_128_CCM_SHA256"]},"keyLength":{"unit":"number","value":128}}}]}
returns the following error
{"timestamp":"2019-11-26T15:05:19.516+0000","status":400,"error":"Bad Request","message":"JSON parse error: Cannot deserialize instance of java.lang.Stringout of START_ARRAY token; nested exception is com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize instance ofjava.lang.String out of START_ARRAY token\n at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: de.tub.privacySecurityEvaluator.model.Request[\"requirement\"]->de.tub.privacySecurityEvaluator.model.fields.AlgorithmField[\"value\"])","path":"/v1/filter"}
This issue appears to be present only in the staging environment, so I suspect an older version of that component to be deployed there.
The PSE fails to correctly parse requests. For instance, the following request
{"requirement":{"id":"encryption_AES128","description":"Encryption AES 128","type":"TransportEncryption","properties":{"protocol":{"unit":"enum","value":"TLS"},"algorithm":{"unit":"list","value":["TLS_AES_256_GCM_SHA384","TLS_AES_128_GCM_SHA256","TLS_AES_128_CCM_8_SHA256","TLS_AES_128_CCM_SHA256"]},"keyLength":{"unit":"number","value":128}}},"blueprintAttributes":[{"id":"encryption_AES128","description":"Encryption AES 128","type":"TransportEncryption","properties":{"protocol":{"unit":"enum","value":"TLS"},"algorithm":{"unit":"list","value":["TLS_AES_256_GCM_SHA384","TLS_AES_128_GCM_SHA256","TLS_AES_128_CCM_8_SHA256","TLS_AES_128_CCM_SHA256"]},"keyLength":{"unit":"number","value":128}}}]}returns the following error
{"timestamp":"2019-11-26T15:05:19.516+0000","status":400,"error":"Bad Request","message":"JSON parse error: Cannot deserialize instance ofjava.lang.Stringout of START_ARRAY token; nested exception is com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize instance ofjava.lang.Stringout of START_ARRAY token\n at [Source: UNKNOWN; line: -1, column: -1] (through reference chain: de.tub.privacySecurityEvaluator.model.Request[\"requirement\"]->de.tub.privacySecurityEvaluator.model.fields.AlgorithmField[\"value\"])","path":"/v1/filter"}This issue appears to be present only in the staging environment, so I suspect an older version of that component to be deployed there.