Chaining of Processors

Local Edition can support multiple pre-processing and post-processing processors per endpoint. This is done by linking multiple processors into one configuration. The entire process is called Chaining.

Note: You can chain only pre-processing and post-processing events. The authentication event cannot be chained.
The following table describes chaining between different events.
Pre Process Event Post Process Event Authentication Event
Pre Process Event
Post Process Event
Authentication Event

Types of Chaining

  • Chaining Processor Using Mashery_Proxy_Processor_Chain

    The processor implements pre-process or post-process traffic events. These processors can either be provided by TIBCO or incorporated with the SDK.

    To chain the processors use Mashery_Proxy_Processor_Chain.

  • Chaining of Processor Using Chain Adapter

    These processors can implement pre-process or post-process traffic events and can be chained without using Mashery_Proxy_Processor_Chain and are provided by TIBCO.

    The following are processors acting as chain adapter provided by TIBCO.
    • OAuth2JWT Authentication Connector
    • OAuth2 Shared Token Connector
The following table provides information on various chaining combinations.
SDK Based Adapters TIBCO Provided Adapters Chain Adapter OAuth2JWTAuthenticationConnector Chain Adapter OAuth2SharedTokenConnector
SDK Based Adapters

Using Mashery_Proxy_Processor_Chain

Using Mashery_Proxy_Processor_Chain

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

TIBCO Provided Adapters

Using Mashery_Proxy_Processor_Chain

Using Mashery_Proxy_Processor_Chain

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Chain Adapter OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector

Chain Adapter OAuth2SharedTokenConnector

Using OAuth2JWTAuthenticationConnector

Using OAuth2JWTAuthenticationConnector