This section introduces handlers and using an example, explains how to write a custom handler:
When an API is created, a file with its synapse configuration is added to the API Gateway. You can find it in the
<APIM_HOME>/repository/deployment/server/synapse-configs/default/api folder. It has a set of handlers, each of which is executed on the APIs in the same order they appear in the configuration. You find the default handlers in any API's Synapse definition as shown below.
Let's see what each handler does:
Sets the CORS headers to the request and executes the CORS sequence mediation logic. This handler is thereby responsible for returning the CORS headers from the gateway or routing the requests to the backend and letting the backend send the CORS headers.
APIAuthenticationHandler:Validates the OAuth2 bearer token used to invoke the API. It also determines whether the token is of type
MessageContextvariables as appropriate.
APIThrottleHandler:Throttles requests based on the throttling policy specified by the
policyKeyproperty. Throttling is applied both at the application level as well as subscription level.
APIMgtUsageHandler:Publishes events to WSO2 Data Analytics Server (WSO2 DAS) for collection and analysis of statistics. This handler only comes to effect if . See Working with Statistics for more information.
APIMgtGoogleAnalyticsTrackingHandler:Publishes events to Google Analytics. This handler only comes into effect if Google analytics tracking is enabled. See for more information.
APIManagerExtensionHandler: Triggers extension sequences. By default, the extension handler is listed at last in the handler chain, and therefore is executed last. You cannot change the order in which the handlers are executed, except the extension handler. To configure the API Gateway to execute extension handler first, uncomment the
<ExtensionHandlerPosition>section in the
<APIM_HOME>/repository/conf/api-manager.xmlfile and provide the value
top. This is useful when you want to execute your own extensions before our default handlers in situations like doing additional security checks such as signature verification on access tokens before executing the default security handler.
See Adding Mediation Extensions.
Writing a custom handler
Let's see how you can write a custom handler and apply it to the API Manager. In this example, we extend the authentication handler. Make sure your custom handler name is not the same as the name of an existing handler.
WSO2 API Manager provides the OAuth2 bearer token as its default authentication mechanism. A sample implementation is here. Similarly, you can extend the API Manager to support any custom authentication mechanism by writing your own authentication handler class. This custom handler must extend
org.apache.synapse.rest.AbstractHandler class and implement the
Given below is an example implementation:
Engaging the custom handler
You can engage a custom handler to all APIs at once or only to selected APIs.
To engage to all APIs, the recommended approach is to add it to the
<APIM_HOME>/repository/resources/api_templates/velocity_template.xml file. For example, the following code segment adds the custom authentication handler that you wrote earlier to the
velocity_template.xml file while making sure that it skips the default
Given below is how to engage handlers to a single API, by editing its source view.
Note that when you engage a handler by editing the API's source view, your changes will be overwritten every time you save the API through the API Publisher.
- Build the class and copy the JAR file to
- Log in to the management console and click Service Bus > Source View in the Main menu.
In the configuration that opens, select an API and navigate to the
The second handler is the current authentication handler used in the API Manager. Replace the second handler with the handler that you created. It will engage your custom handler to the API Manager instance. According to this example, it is as follows: