Dynamically setting elements in the JSON Threat Protection policy.

Google Cloud Apigee
,
1

Hello,

I am looking to implement a JSON Threat Protection policy within a shared flow in Apigee. I have the policy defined within the flow using the default settings of the policy; however, I would like to be able to dynamically set the different elements (ArrayElementCount, ContainerDepth, ObjectEntryCount, etc…) within the policy using variables that will be read from a .properties file. The variables from the properties file are being set and read correctly, but when they are referenced in the policy, the elements within the JSON Threat Protection policy no longer work as intended/expected. I noticed this thread with a similar question/concept to what I am asking here, but the general response from the Staff was that the JSON Threat Protection policy doesn’t support the use of ref variables. I would like to know if this is still the case and whether there are any plans in the future to implement this important feature.

2

https://www.googlecloudcommunity.com/gc/Apigee/is-values-for-element-in-the-quot-JsonThreatProtection-quot/td-p/798547

3

I added below properties in my JSONThreatProtection Policy and it is working somehow and picking the values from KVM, even though these attributes are not defined in APIGEE documentation. What could be the reason for it?

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> jsontp-validator {maxMessageSize} {maxElementDepth} {maxStringLength} {maxArrayElements} {maxObjectProperties}
4

??? that’s not how you configure the JSONThreatProtection policy. It’s documented here: [https://cloud.google.com/apigee/docs/api-platform/reference/policies/json-threat-protection-policy#elementreference](https://cloud.google.com/apigee/docs/api-platform/reference/policies/json-threat-protection-policy#elementreference)

Where did you get the stuff you are using?

Are you an AI making false posts?