Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Fixed a typo in the title:
https://docs.wso2.org/display/AM170/Configuring+Caching#Clearing the API
Gateway cache
On Mon, May 26, 2014 at 2:49 PM, Nirdesha Munasinghe wrote:
> Thanks, Sanjeewa. I added this infor in [1].
>
> Samuel, if relevant, please point to this section from the clustering
> guide too. This is about how to clear the API Gateway cache and the steps
> actually explain how to configure this in a clustered APIM setup.
>
> [1] https://docs.wso2.org/display/AM170/Configuring+Caching#Claring API
> Gateway cache
>
>
>
> On Fri, May 23, 2014 at 1:19 AM, Sanjeewa Malalgoda wrote:
>
>>
>>
>>
>> On Mon, May 19, 2014 at 11:57 AM, Nirdesha Munasinghe
>> wrote:
>>
>>> Thanks for reporting. Doc JIRA created:
>>> https://wso2.org/jira/browse/DOCUMENTATION-842.
>>>
>>>
>>> On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda
>>> wrote:
>>>
Hi All,
We found following issues in gateway cache when we regenerate
application tokens from API store user interface(or calling revoke API).
01. If we generate new application access token from ui old tokens
remain as active in gateway cache.
02. If we use revoke API deployed in gateway it will clear only super
tenants cache.
hi Nirdesha,
>> Please note following change in this configurations.
>>
>>> To address these issues recently we introduced new parameter named
RevokeAPIURL. In distributed deployment we need to configure this parameter
in API key manager node. Then it will call API pointed by RevokeAPIURL
parameter. RevokeAPIURL parameter should be pointed to revoke API deployed
API gateway nodes. If it is gateway cluster we can point to one node. So
from this release on wards all revoke requests will route to oauth service
through revoke API deployed in API manager. When revoke response route
through revoke API cache clear handler will invoke. Then it will extract
relevant information form transport headers and clear associated cache
entries. In distributed deployment we should configure followings.
01. In key manager node, point gateway API revoke end point as follows.
https://
${carbon.local.ip}:${https.nio.port}/revoke
02. In API gateway revoke API should be pointed to oauth application
deployed in key manager node.
>>> faultSequence="_token_fault_">
https://keymgt.wso2.com:9445/oauth2/revoke"/>
>>> class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
We need to add this to our product documents as well.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Thanks, Sanjeewa. I added this infor in [1].
Samuel, if relevant, please point to this section from the clustering guide
too. This is about how to clear the API Gateway cache and the steps
actually explain how to configure this in a clustered APIM setup.
[1] https://docs.wso2.org/display/AM170/Configuring+Caching#Claring API
Gateway cache
On Fri, May 23, 2014 at 1:19 AM, Sanjeewa Malalgoda wrote:
>
>
>
> On Mon, May 19, 2014 at 11:57 AM, Nirdesha Munasinghe
> wrote:
>
>> Thanks for reporting. Doc JIRA created:
>> https://wso2.org/jira/browse/DOCUMENTATION-842.
>>
>>
>> On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda wrote:
>>
>>> Hi All,
>>> We found following issues in gateway cache when we regenerate
>>> application tokens from API store user interface(or calling revoke API).
>>>
>>> 01. If we generate new application access token from ui old tokens
>>> remain as active in gateway cache.
>>> 02. If we use revoke API deployed in gateway it will clear only super
>>> tenants cache.
>>>
>>> hi Nirdesha,
> Please note following change in this configurations.
>
>> To address these issues recently we introduced new parameter named
>>> RevokeAPIURL. In distributed deployment we need to configure this parameter
>>> in API key manager node. Then it will call API pointed by RevokeAPIURL
>>> parameter. RevokeAPIURL parameter should be pointed to revoke API deployed
>>> API gateway nodes. If it is gateway cluster we can point to one node. So
>>> from this release on wards all revoke requests will route to oauth service
>>> through revoke API deployed in API manager. When revoke response route
>>> through revoke API cache clear handler will invoke. Then it will extract
>>> relevant information form transport headers and clear associated cache
>>> entries. In distributed deployment we should configure followings.
>>>
>>> 01. In key manager node, point gateway API revoke end point as follows.
>>>
>>> https://
>>> ${carbon.local.ip}:${https.nio.port}/revoke
>>>
>>> 02. In API gateway revoke API should be pointed to oauth application
>>> deployed in key manager node.
>>>
>>> >> faultSequence="_token_fault_">
>>>
>>>
>>>
>>> https://keymgt.wso2.com:9445/oauth2/revoke"/>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> >> class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
>>>
>>>
>>>
>>> We need to add this to our product documents as well.
>>>
>>>
>>> Thanks,
>>> sanjeewa.
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
On Mon, May 19, 2014 at 11:57 AM, Nirdesha Munasinghe wrote:
> Thanks for reporting. Doc JIRA created:
> https://wso2.org/jira/browse/DOCUMENTATION-842.
>
>
> On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda wrote:
>
>> Hi All,
>> We found following issues in gateway cache when we regenerate application
>> tokens from API store user interface(or calling revoke API).
>>
>> 01. If we generate new application access token from ui old tokens remain
>> as active in gateway cache.
>> 02. If we use revoke API deployed in gateway it will clear only super
>> tenants cache.
>>
>> hi Nirdesha,
Please note following change in this configurations.
> To address these issues recently we introduced new parameter named
>> RevokeAPIURL. In distributed deployment we need to configure this parameter
>> in API key manager node. Then it will call API pointed by RevokeAPIURL
>> parameter. RevokeAPIURL parameter should be pointed to revoke API deployed
>> API gateway nodes. If it is gateway cluster we can point to one node. So
>> from this release on wards all revoke requests will route to oauth service
>> through revoke API deployed in API manager. When revoke response route
>> through revoke API cache clear handler will invoke. Then it will extract
>> relevant information form transport headers and clear associated cache
>> entries. In distributed deployment we should configure followings.
>>
>> 01. In key manager node, point gateway API revoke end point as follows.
>>
>> https://
>> ${carbon.local.ip}:${https.nio.port}/revoke
>>
>> 02. In API gateway revoke API should be pointed to oauth application
>> deployed in key manager node.
>>
>> > faultSequence="_token_fault_">
>>
>>
>>
>> https://keymgt.wso2.com:9445/oauth2/revoke"/>
>>
>>
>>
>>
>>
>>
>>
>>
>> > class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
>>
>>
>>
>> We need to add this to our product documents as well.
>>
>>
>> Thanks,
>> sanjeewa.
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>
Re: [Dev] Gateway cache clearing for regenerated and revoked tokens
Thanks for reporting. Doc JIRA created:
https://wso2.org/jira/browse/DOCUMENTATION-842.
On Sat, May 17, 2014 at 8:49 PM, Sanjeewa Malalgoda wrote:
> Hi All,
> We found following issues in gateway cache when we regenerate application
> tokens from API store user interface(or calling revoke API).
>
> 01. If we generate new application access token from ui old tokens remain
> as active in gateway cache.
> 02. If we use revoke API deployed in gateway it will clear only super
> tenants cache.
>
> To address these issues recently we introduced new parameter named
> RevokeAPIURL. In distributed deployment we need to configure this parameter
> in API store node. Then it will call API pointed by RevokeAPIURL parameter.
> RevokeAPIURL parameter should be pointed to revoke API deployed API gateway
> nodes. If it is gateway cluster we can point to one node. So from this
> release on wards all revoke requests will route to oauth service through
> revoke API deployed in API manager. When revoke response route through
> revoke API cache clear handler will invoke. Then it will extract relevant
> information form transport headers and clear associated cache entries. In
> distributed deployment we should configure followings.
>
> 01. In key manager node, point gateway API revoke end point as follows.
>
> https://
> ${carbon.local.ip}:${https.nio.port}/revoke
>
> 02. In API gateway revoke API should be pointed to oauth application
> deployed in key manager node.
>
> faultSequence="_token_fault_">
>
>
>
> https://keymgt.wso2.com:9445/oauth2/revoke"/>
>
>
>
>
>
>
>
>
> class="org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerCacheExtensionHandler"/>
>
>
>
> We need to add this to our product documents as well.
>
>
> Thanks,
> sanjeewa.
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>
[Dev] Gateway cache clearing for regenerated and revoked tokens
Hi All,
We found following issues in gateway cache when we regenerate application
tokens from API store user interface(or calling revoke API).
01. If we generate new application access token from ui old tokens remain
as active in gateway cache.
02. If we use revoke API deployed in gateway it will clear only super
tenants cache.
To address these issues recently we introduced new parameter named
RevokeAPIURL. In distributed deployment we need to configure this parameter
in API store node. Then it will call API pointed by RevokeAPIURL parameter.
RevokeAPIURL parameter should be pointed to revoke API deployed API gateway
nodes. If it is gateway cluster we can point to one node. So from this
release on wards all revoke requests will route to oauth service through
revoke API deployed in API manager. When revoke response route through
revoke API cache clear handler will invoke. Then it will extract relevant
information form transport headers and clear associated cache entries. In
distributed deployment we should configure followings.
01. In key manager node, point gateway API revoke end point as follows.
https://
${carbon.local.ip}:${https.nio.port}/revoke
02. In API gateway revoke API should be pointed to oauth application
deployed in key manager node.
https://keymgt.wso2.com:9445/oauth2/revoke"/>
We need to add this to our product documents as well.
Thanks,
sanjeewa.
--
*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779
