If we consider the case of enabling token caching on the Gateway, the
reason we do that is to avoid a call being made to the key manager. But if
it requires to make a call to the key manager for the sake of generating
the JWT token, the purpose of having token caching on the Gateway is lost.
Therefore I don't think disabling the JWT cache while the Gateway token
cache is enabled is a valid use case.
Thanks,
NuwanD.
On Sat, Sep 14, 2013 at 11:05 AM, Ushani Balasooriya ush...@wso2.comwrote:
Hi,
I need to test JWTCache in AM. Therefore I have enabled GatewayKeyCache
and disabled JWTCache in api-manager.xml and invoked an API via an
application then changed the application name and invoked again. Then
decoded the response. But still the application name is not changed
even-though I have disabled the JWTCache property.
When I enabled both GatewayKeyCache and JWTCache still the response will
be cached.
Is this expected or a bug and is this the correct way to test JWTCache
in AM or what are the values that will be taken from the JWT cache?
Thanks!
--
*Ushani Balasooriya*
Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; +94772636796
--
Nuwan Dias
Senior Software Engineer - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
