When an API call hits the API Gateway, the Gateway carries out security checks to verify if the token is valid. During these verifications, the API Gateway extracts parameters such as access token, API and API version that are passed on to it. Since the entire load of traffic to APIs goes through the API Gateway, this verification process needs to be fast and efficient in order to prevent overhead and delays. The API Manager uses caching for this purpose, where the validation information is cached with the token, API name and version, and the cache is stored in either the API Gateway or the key manager server.
This section covers the following:
Apart from response caching, all the other caches are enabled by product. When the API Manager components are clustered, they work as distributed caches. This means that a change done by one node is visible to another node in the cluster.
API Gateway cache
When c and a request hits the Gateway, it first populates the cached entry for a given token. If a cache entry does not exist in cache, it calls the key manager server. This process is carried out using Web service calls. Once the key manager server returns the validation information, it gets stored in the Gateway. Because the API Gateway issues a Web service call to the key manager server only if it does not have a cache entry, this method reduces the number of Web service calls to the key manager server. Therefore, it is faster than the alternative method.
By default, the API Gateway cache is enabled by setting the
<EnableGatewayKeyCache> element to true in
Clearing the API Gateway cache
To remove old tokens that might still remain active in the Gateway cache, you configure the
<RevokeAPIURL> element in
api-manager.xml file by providing the URL of the Revoke API that is deployed in the API Gateway node. The revoke API invokes the cache clear handler, which extracts information form transport headers of the revoke request and clears all associated cache entries. If there's a cluster of API Gateways in your setup, provide the URL of the revoke API deployed in one node in the cluster. This way, all revoke requests route to the OAuth service through the Revoke API.
Given below is how to configure this in a distributed API Manager setup.
api-manager.xmlfile of the key manager node, point the revoke endpoint as follows:
In the API Gateway, point the Revoke API to the OAuth application deployed in the key manager node. For example,
An API's resources are HTTP methods that handle particular types of requests such as GET, POST etc. They are similar to methods of a particular class. Each resource has parameters such as its throttling level, Auth type etc.
Users can make requests to an API by calling any one of the HTTP methods of the API's resources. The API Manager uses the resource cache at the Gateway node to store the API's resource-level parameters (Auth type and throttling level). The cache entry is identified by a cache key, which is based on the API's context, version, request path and HTTP method. Caching avoids the need to do a separate back-end call to check the Auth type and throttling level of a resource, every time a request to the API comes. It improves performance.
Note that if you change a resource's parameters such as the Auth type through the UI, it takes about 15 minutes to refresh the resource cache. During that time, the server returns the old Auth type from the cache. If you want the changes to be reflected immediately, please restart the server after changing the value.
By default, the resource cache is enabled by setting the
<EnableGatewayResourceCache> element to true in
Key Manager cache
The following caches are available:
In a typical API Manager deployment, the Gateway is deployed in a DMZ while the Key Manager is in MZ. By default, caching is enabled at the Gateway. If you do not like to cache token related information in a leniently secured zone, you can do that on the Key Manager side. In this method, for each and every API call that hits the API Gateway, the Gateway issues a Web service call to the Key Manager server. If the cache entry is available in the Key Manager server, it is returned to the Gateway. Else, the database will be checked for the validity of the token.
This method has low performance compared to the earlier one, but you do not have to store any security-related information at the Gateway side. Using this cache combined with the Gateway cache is not recommended.
Disable caching at the API Gateway by adding the following entry to the APIGateway section of the
Enable the Key Manager cache by adding the following entry to the APIKeyManager section of the api-manager.xml file.
You sometimes pass certain enduser attributes to the backend using JSON Web Tokens (JWT). If you enable JWT generation, the token is generated in the Key Manager server for each validation information object and is sent as part of the key validation response. Usually, the JWT also gets cached with the validation information object, but you might want to generate JWTs per each call. You can do this by enabling JWT caching at key manager server. Add the following entry to APIKeyManager section of the
You must disable caching at the Key Manager server side in order to generate JWTs per each call. Disabling the JWT cache only works if you have enabled the Key Manager cache, which is disabled by default.
Also enable token generation by setting the following entry to
true at the root level of the api-manager.xml file.
The OAuth token is saved in this cache, which is enabled by default. Whenever a new OAuth token is generated, it is saved in this cache to prevent constant database calls. Unless an OAuth expires or is revoked, the same token is sent back for the same user. Therefore, you do not need to change this cached token most of the time.
The API Manager uses WSO2 ESB's cache mediator to cache response messages per each API. Caching improves performance, because the backend server does not have to process the same data for a request multiple times. To offset the risk of stale data in the cache, you set an appropriate timeout period.
You enable response caching when creating a new API or editing an existing one using the API Publisher UI. Go to the API Publisher and click the Add API menu (to create a new API) or the Edit link associated with an existing API. Then, navigate to the Manage tab where you find the response caching section. You can set it to
Enabled and give a timeout value. This enables the default response caching settings.
To change the default response caching settings, edit the following cache mediator properties in
|Specifies the maximum size of a message to be cached in bytes. An optional attribute, with the default value set to |
|maxSize||Defines the maximum number of elements to be cached|
Defines the hash generator class.
When caching response messages, a hash value is generated based on the request's URI, transport headers and the payload (if available). WSO2 has a default
If you want to change this default implementation (for example, to exclude certain headers), you can write a new hash generator implementation by extending the
API Store cache
The API Store has several caches to reduce the page-load times and increase its responsiveness when multiple users access it simultaneously.
Tag cache: This cache saves the API's tags after they have been retrieved from registry. If your APIs and associated tags change frequently, it is recommended to configure a smaller cache refresh time (in milliseconds). This cache disabled by default. To enable it, uncomment the
<TagCacheDuration>element in the
Recently-added-API cache: This cache saves the recently added APIs. It is disabled by default. If you have multiple API modifications during a short time period, it is recommended to not enable this cache. To enable it, set the <EnableRecentlyAddedAPICache> to true in the