Search Results

Mashery Local Porting and Chaining

Mashery Local Porting

This Connector can be ported to Mashery Local customer specific bundle.
Note: Porting of this Connector can be performed by TIBCO Mashery® for a specific Mashery Local customer. For more information, consult TIBCO Mashery® Customer Success team.

Chaining

  • HTTP Basic Authentication connector natively supports chaining and can be chained with existing Customer processors as well as Connectors Mashery developed and available. For example, if you want to chain REST <-> SOAP Transformation Connector with HTTP Basic Authentication connector, you can do the following: (Sample reference only)
  • Processing adapter: com.mashery.proxy.customer.generic.http-basic-auth
  • Perform Pre-processing: Enabled
  • Data to make available for pre-processing (one per line). sample/example.
    • processors:com.mashery.proxy.customer.generic.rest-soap-transformation-connector
    • com.mashery.proxy.customer.generic.rest-soap-transformation-connector.soap_protocol:1.1
    • Keep_Mashery_Default_Response_Code:true

Caution:

  • Do not chain HTTP Basic Authenticator with: com.mashery.proxy.customer.generic.oauth2-shared-token-adapter / com.mashery.proxy.customer.generic.oauth2-jwt-authenticator.

    All three - HTTP Basic Authenticator, OAuth2JWT authenticator and OAuth2 Shared token adapter - natively support chaining and will not work after chaining.

  • Do not chain HTTP Basic Authenticator with: com.mashery.proxy.customer.generic.JWTAuthProcessor / com.mashery.proxy.customer.generic.oauth-token-validation-connector.

    All three - HTTP Basic Authenticator, JWT Auth Processor and OAuth2.0 Token Validation connector - require token in Authorization header and if used simultaneously, will not work properly.