diff --git a/en/docs/assets/img/learn/mediation-json-validator.png b/en/docs/assets/img/learn/mediation-json-validator.png index b512d1075e..9b7b2165eb 100644 Binary files a/en/docs/assets/img/learn/mediation-json-validator.png and b/en/docs/assets/img/learn/mediation-json-validator.png differ diff --git a/en/docs/assets/img/learn/mediation-regex-policy.png b/en/docs/assets/img/learn/mediation-regex-policy.png index 00fa30e915..486e52d361 100644 Binary files a/en/docs/assets/img/learn/mediation-regex-policy.png and b/en/docs/assets/img/learn/mediation-regex-policy.png differ diff --git a/en/docs/assets/img/learn/mediation-xml-validator.png b/en/docs/assets/img/learn/mediation-xml-validator.png index 987af14f9e..e813114fa6 100644 Binary files a/en/docs/assets/img/learn/mediation-xml-validator.png and b/en/docs/assets/img/learn/mediation-xml-validator.png differ diff --git a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway.md b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway.md index 9b1ca962c2..965c4aab4e 100644 --- a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway.md +++ b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway.md @@ -35,27 +35,25 @@ is given below. To edit the existing sequence follow the steps below. -1. Log in to the Management Console. -2. Navigate to `/_system/governance/apimgt/customsequences/in/json_validator.xml ` -3. Edit the `json_validator.xml` file. -4. Go to the API Publisher and re-publish your API for the changes to take effect. +1. Go to **Policies** section in the Publisher Portal. +2. Add a new policy with the name **JSON Validator** and provide an newer version. +3. Upload the Policy File with the required changes. +4. Click **Save** to save the newer version of the policy. +5. Apply the newly created policy to the API as per the below section. ### Applying the JSON validator policy You can apply the predefined JSON Policy through the UI. Follow the instructions below to apply the json\_validator in sequence. -- Create an API or edit an existing API. +1. Create an API or edit an existing API. +2. Go to **Policies** under the **API Configuration** sub-section from the left hand panel. +3. As required, drag and drop the **JSON Validator** from the Policy List tab into Request Flow. +4. Provide the required parameters for JSON validation. -- Go to **Message Mediation** Policies under **Request** configurations of the **Runtime Configurations** tab. - -- Select **Edit** the message mediation bar and select **Common Policies** . - -- Select `json\_validator` from the drop-down menu for Common Policies. - - Select JSON validator from the drop-down menu - -- Scroll down the page and click **Save** to save the changes. + Drag and drop the JSON Validator from the policy list + +4. Scroll down the page and click **Save** to save the changes (click **Save and Deploy** and deploy the API for the changes to take effect in the gateways). ### Testing the JSON threat protector diff --git a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway.md b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway.md index beaa89702f..52e28b2b95 100644 --- a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway.md +++ b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway.md @@ -71,24 +71,24 @@ We recommend the following patterns for denying requests. To edit the existing sequence follow the steps below. -1. Log in to the Management Console. -2. Navigate to `/_system/governance/apimgt/customsequences/in/regex_policy.xml` -3. Edit the `regex_policy.xml` file. -4. Go to the API Publisher and re-publish your API for the changes to take effect. +1. Go to **Policies** section in the Publisher Portal. +2. Add a new policy with the name **Regex Policy** and provide an newer version. +3. Upload the Policy File with the required changes. +4. Click **Save** to save the newer version of the policy. +5. Apply the newly created policy to the API as per the below section. ### Applying the Regular Expression Policy You can apply the predefined Regular Expression Policy through the UI. Follow the instructions below to apply the regex\_policy in sequence. -1. Create an API or edit an existing API. -2. Go to **Message Mediation** Policies under **Request** configurations of the **Runtime Configurations** tab. -3. Select **Edit** in the message mediation bar and select **Common Policies** . -4. Select `regex_policy` from the drop-down menu for Common Policies. +1. Create an API or edit an existing API. +2. Go to **Policies** under the **API Configuration** sub-section from the left hand panel. +3. As required, drag and drop the **Regex Policy** from the Policy List tab into Request Flow. - Select Regex policy from the drop-down menu + Drag and drop the Regex Policy from the policy list -4. Scroll down the page and click **Save** to save the changes. +4. Scroll down the page and click **Save** to save the changes (click **Save and Deploy** and deploy the API for the changes to take effect in the gateways). Each request is sanitized through the regular expression threat protector. You can add or modify the regex patterns according to your requirement. diff --git a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway.md b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway.md index 7bd4ad66ee..36f63f8205 100644 --- a/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway.md +++ b/en/docs/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway.md @@ -86,28 +86,24 @@ your requirement. To edit the existing sequence follow the steps below. -1. Log in to the Management Console. -2. Navigate to `/_system/governance/apimgt/customsequences/in/xml_validator.xml` -3. Edit the `xml_validator.xml` file. -4. Go to the API Publisher and re-publish your API for the changes to take effect. +1. Go to **Policies** section in the Publisher Portal. +2. Add a new policy with the name **XML Validator** and provide an newer version. +3. Upload the Policy File with the required changes. +4. Click **Save** to save the newer version of the policy. +5. Apply the newly created policy to the API as per the below section. ### Applying the XML validator policy You can apply the predefined XML Policy through the UI. Follow the instructions below to apply the xml\_validator in sequence. -- Create an API or edit an existing API. - -- Go to **Message Mediation** Policies under **Request** configurations of the **Runtime Configurations** tab. - -- Select **Edit** in the message mediation bar and select **Common Policies** . - -- Select `xml_validator` from the drop-down menu for Common Policies. - - Select XML validator from the drop-down menu +1. Create an API or edit an existing API. +2. Go to **Policies** under the **API Configuration** sub-section from the left hand panel. +3. As required, drag and drop the **XML Validator** from the Policy List tab into Request Flow. + Drag and drop the XML Validator from the policy list -- Scroll down the page and click **Save** to save the changes. +4. Scroll down the page and click **Save** to save the changes (click **Save and Deploy** and deploy the API for the changes to take effect in the gateways). ### Testing the XML threat protector