如何控制Mule Cache中的密钥生成

时间:2015-03-06 00:31:33

标签: caching mule

我的要求是将用户(使用外部ws)作为我的Mule Flow的一部分进行身份验证,并在缓存中使用身份验证的结果。但是,如果用户凭据发生更改,则应自动使缓存失效,并且必须使用外部ws完成用户身份验证。基本上,缓存键应基于用户凭据。这可能吗 ?

这是我的骡子流,我看到Mule在第一次请求后缓存结果,无论后续请求中的有效负载是否发生变化(这是发送凭据的位置),mule总是返回结果从缓存。因此,当第一个请求具有不正确的凭据时,用户身份验证失败并且mule缓存响应。从此时起,无论在后续请求中发送正确的凭据,它始终引用缓存并返回用户身份验证失败。我如何实现我想要实现的目标?

这是我的骡子流:

    <?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:json="http://www.mulesoft.org/schema/mule/json" xmlns:scripting="http://www.mulesoft.org/schema/mule/scripting" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:tracking="http://www.mulesoft.org/schema/mule/ee/tracking" xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
    xmlns:spring="http://www.springframework.org/schema/beans" version="EE-3.6.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd
http://www.mulesoft.org/schema/mule/ee/tracking http://www.mulesoft.org/schema/mule/ee/tracking/current/mule-tracking-ee.xsd
http://www.mulesoft.org/schema/mule/scripting http://www.mulesoft.org/schema/mule/scripting/current/mule-scripting.xsd
http://www.mulesoft.org/schema/mule/json http://www.mulesoft.org/schema/mule/json/current/mule-json.xsd">
    <http:listener-config name="HTTP-Inbound-Endpoint" host="0.0.0.0" port="8888" doc:name="HTTP Listener Configuration"/>
    <http:request-config name="HTTP_Request_Configuration" host="10.10.10.10" port="8080" doc:name="HTTP Request Configuration"/>
    <ee:object-store-caching-strategy name="Auth-Cache-Strategy" doc:name="Caching Strategy">
        <in-memory-store name="UserAuthCache" maxEntries="100" entryTTL="3600" expirationInterval="3600"/>
    </ee:object-store-caching-strategy>
    <flow name="cacheauthenticationFlow">
        <http:listener config-ref="HTTP-Inbound-Endpoint" path="*" doc:name="HTTP"/>
        <object-to-string-transformer doc:name="Object to String"/>
        <ee:cache cachingStrategy-ref="Auth-Cache-Strategy" doc:name="Cache">
            <logger message="Incoming: #[message.payload]" level="INFO" doc:name="Logger"/>
            <scripting:transformer doc:name="Python">
                <scripting:script engine="jython"><![CDATA[import base64
authorization = message.getInboundProperty("authorization")
#print "Authorization is: \"" + authorization + "\""
authstring = authorization.split()
#print authstring
credentials = authstring[-1]
#print "Credentials => " + credentials

decodedAuth = credentials.decode('base64')
#print decodedAuth
if (decodedAuth.find("@") > 0):
    (id, password) = decodedAuth.split(":")
    (username, project) = id.split("@")
    print username + ":" + password + ", Project: " + project
else:
    (username, password) = decodedAuth.split(":")
    print username + ":" + password

message.payload = { "username" : username + "@" + project , "password" : password }
result = message]]></scripting:script>
            </scripting:transformer>
            <json:object-to-json-transformer doc:name="Object to JSON"/>
            <logger message="Incoming payload: #[message.payload]" level="INFO" doc:name="Logger"/>
            <http:request config-ref="HTTP_Request_Configuration" path="/wservices/authenticate/user" method="POST" doc:name="HTTP-Dev-Box-Authentication"/>
            <object-to-string-transformer doc:name="Object to String"/>
        </ee:cache>
        <logger message="Response From Cache: #[message.payload]" level="INFO" doc:name="Logger"/>
        <set-payload value="#[message.payload.'status']" doc:name="Response"/>
    </flow>
</mule>

2 个答案:

答案 0 :(得分:0)

由于缓存作用域的默认密钥生成策略基于消息有效内容,因此在您的特定情况下,只需移动scripting:transformer即可在ee:cache作用域之前执行。

对于更通用的解决方案,您不希望覆盖请求有效负载,可以在keyGenerationExpression元素上定义keyGenerator-refee:cache属性以控制缓存密钥的方式我生成了。

例如,要使用完整的HTTP授权标头作为密钥,您可以使用:

 <ee:cache cachingStrategy-ref="Auth-Cache-Strategy" doc:name="Cache"
      keyGenerationExpression="#[message.inboundProperties.authorization]">
     <!-- Your flow here --> 
 </ee:cache>

有关详细信息,请参阅cache scope documentation

如果你想使用这种方法,你可以做的是将jython代码的一部分移到缓存范围之外,更改它以便它将用户和密码设置为消息上的单独流变量,然后在{{{{{ 1}}然后再在一个简单的keyGenerationExpression变换器的缓存范围内。

答案 1 :(得分:0)

您可以定义全局配置&#34; Caching_Strategy&#34;

SELECT * FROM game_tbl WHERE ( `player_o` = 1 OR `player_x` = 1 ) AND ( `player_o` = NULL OR `player_x` = NULL )

并在缓存流程中引用全局配置:

<ee:object-store-caching-strategy name="Caching_Strategy" keyGenerationExpression="#[flowVars.userID]" doc:name="Caching Strategy"/>

您可以通过流变量#[flowVars.userID]

来控制您的keyGenerationExpression

有关完整详细信息,请参阅示例 http://www.tutorialsatoz.com/caching-in-mule-cache-scope/