WSO2-策略的节流中介器实现未阻止来自IP的请求

如何解决WSO2-策略的节流中介器实现未阻止来自IP的请求

我一直在努力应对WSO2节流中介，并使用WSO2文档进行了设置。尽管如此，我仍无法达到实现该政策效果的预期目标。

尽管有代码，但是该策略表示如下内容：

IF请求来自IP = {{MY_IP}}，请求计数
然后调用端点/序列（AcceptSequence）->在此，将调用端点
ELSE IF请求计数> 10，则请求将记录在数据库中。

我已经分别测试了端点的接受序列和EI Dataservice的rejectSequence，并且工作正常。我什至可以在EI wso2carbon日志中看到请求，但是没有节流调解器调用的迹象，并且正在返回“ 202 Accepted”

<?xml version="1.0" encoding="UTF-8"?>
<api context="/my_api" name="MY_API" version="1.0.0" version-type="context" xmlns="http://ws.apache.org/ns/synapse">
    <resource methods="POST">
        <inSequence>
            <log level="custom">
                <property expression="json-eval($)" name="Incoming Payload"/>
            </log>
            <property description="Client_Name" expression="$trp:Client_Name" name="Client_Name" scope="default" type="STRING"/>
            <property description="Client_DOB" expression="$trp:Client_DOB" name="Client_DOB" scope="default" type="STRING"/>
            <property description="Client_ID_Type" expression="$trp:Client_ID_Type" name="Client_ID_Type" scope="default" type="STRING"/>
            <property description="Client_ID_No" expression="$trp:Client_ID_No" name="Client_ID_No" scope="default" type="STRING"/>
            <property description="Client_Gender" expression="$trp:Client_Gender" name="Client_Gender" scope="default" type="STRING"/>
            <property description="Client_Nationality" expression="$trp:Client_Nationality" name="Client_Nationality" scope="default" type="STRING"/>
            <property description="Source_System" expression="$trp:Source_System" name="Source_System" scope="default" type="STRING"/>
            <property description="Transaction_Type" expression="$trp:Transaction_Type" name="Transaction_Type" scope="default" type="STRING"/>
            <property description="Transaction_Ref_No" expression="$trp:Transaction_Ref_No" name="Transaction_Ref_No" scope="default" type="STRING"/>
            <property description="Transaction_Ref_No_2" expression="$trp:Transaction_Ref_No_2" name="Transaction_Ref_No_2" scope="default" type="STRING"/>
            <property description="Transaction_Date" expression="$trp:Transaction_Date" name="Transaction_Date" scope="default" type="STRING"/>
        </inSequence>
        <outSequence>
            <throttle id="myThrottle" onAccept="acceptSequence" onReject="rejectSequence">
                <policy>
                    <wsp:Policy wsu:id="WSO2MediatorThrottlingPolicy" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
                        <throttle:MediatorThrottleAssertion xmlns:throttle="http://www.wso2.org/products/wso2commons/throttle">
                            <throttle:MaximumConcurrentAccess>0</throttle:MaximumConcurrentAccess>
                            <wsp:Policy>
                                <throttle:ID throttle:type="IP">{{Required_IP}}</throttle:ID>
                                <wsp:Policy>
                                    <throttle:Control>
                                        <wsp:Policy>
                                            <throttle:MaximumCount>10</throttle:MaximumCount>
                                            <throttle:UnitTime>60000</throttle:UnitTime>
                                            <throttle:ProhibitTimePeriod>60000</throttle:ProhibitTimePeriod>
                                        </wsp:Policy>
                                    </throttle:Control>
                                </wsp:Policy>
                            </wsp:Policy>
                        </throttle:MediatorThrottleAssertion>
                    </wsp:Policy>
                </policy>
            </throttle>
            <log/>
        </outSequence>
        <faultSequence/>
    </resource>
</api>

解决方法

节气门调解器无法按预期方式工作，不是因为节气门调解器出现问题，而是由于您实现此问题的方式。

在inSequence中，您仅定义了日志和某些属性介体。使用此实现，将不会调用outSequence。由于您已在outSequence中实现了节流调解器，并且由于未执行该调解器，因此您可以在不限制请求的情况下调用API。您可以参考一些文档来阐明有关EI消息中介的信息（例如[1]）

仅在以下两种情况下，消息才会从inSequence传递到outSequence。

如果您使用了回送介体[2]
如果您已使用发送中介程序来调用后端。在这种情况下，来自后端的响应将发送到outSequence。

因此，要解决此问题，您有2个选择。

在inSequence的属性中介器的末尾添加回送中介器
按如下所示修改调解，以使油门调解器进入顺序。

<?xml version="1.0" encoding="UTF-8"?>
<api xmlns="http://ws.apache.org/ns/synapse" context="/my_api" name="MY_API" version="1.0.0" version-type="context">
   <resource methods="POST">
      <inSequence>
         <log level="custom">
            <property expression="json-eval($)" name="Incoming Payload" />
         </log>
         <property description="Client_Name" expression="$trp:Client_Name" name="Client_Name" scope="default" type="STRING" />
         <property description="Client_DOB" expression="$trp:Client_DOB" name="Client_DOB" scope="default" type="STRING" />
         <property description="Client_ID_Type" expression="$trp:Client_ID_Type" name="Client_ID_Type" scope="default" type="STRING" />
         <property description="Client_ID_No" expression="$trp:Client_ID_No" name="Client_ID_No" scope="default" type="STRING" />
         <property description="Client_Gender" expression="$trp:Client_Gender" name="Client_Gender" scope="default" type="STRING" />
         <property description="Client_Nationality" expression="$trp:Client_Nationality" name="Client_Nationality" scope="default" type="STRING" />
         <property description="Source_System" expression="$trp:Source_System" name="Source_System" scope="default" type="STRING" />
         <property description="Transaction_Type" expression="$trp:Transaction_Type" name="Transaction_Type" scope="default" type="STRING" />
         <property description="Transaction_Ref_No" expression="$trp:Transaction_Ref_No" name="Transaction_Ref_No" scope="default" type="STRING" />
         <property description="Transaction_Ref_No_2" expression="$trp:Transaction_Ref_No_2" name="Transaction_Ref_No_2" scope="default" type="STRING" />
         <property description="Transaction_Date" expression="$trp:Transaction_Date" name="Transaction_Date" scope="default" type="STRING" />
         <throttle id="myThrottle" onAccept="acceptSequence" onReject="rejectSequence">
            <policy>
               <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:id="WSO2MediatorThrottlingPolicy">
                  <throttle:MediatorThrottleAssertion xmlns:throttle="http://www.wso2.org/products/wso2commons/throttle">
                     <throttle:MaximumConcurrentAccess>0</throttle:MaximumConcurrentAccess>
                     <wsp:Policy>
                        <throttle:ID throttle:type="IP">{{Required_IP}}</throttle:ID>
                        <wsp:Policy>
                           <throttle:Control>
                              <wsp:Policy>
                                 <throttle:MaximumCount>10</throttle:MaximumCount>
                                 <throttle:UnitTime>60000</throttle:UnitTime>
                                 <throttle:ProhibitTimePeriod>60000</throttle:ProhibitTimePeriod>
                              </wsp:Policy>
                           </throttle:Control>
                        </wsp:Policy>
                     </wsp:Policy>
                  </throttle:MediatorThrottleAssertion>
               </wsp:Policy>
            </policy>
         </throttle>
      </inSequence>
      <outSequence>
         <log />
         <send />
      </outSequence>
      <faultSequence />
   </resource>
</api>

[1] -https：//docs.wso2.com/display/EI611/WSO2+Enterprise+Integrator+Best+Practices [2] -https：//ei.docs.wso2.com/en/7.2.0/micro-integrator/references/mediators/loopback-Mediator/

WSO2-策略的节流中介器实现未阻止来自IP的请求

如何解决WSO2-策略的节流中介器实现未阻止来自IP的请求

解决方法

相关推荐