Porting and Chaining
Local Edition Porting
You can port this connector to a customer-specific bundle in the Local Edition.
Cloud API Management can port this connector for a specific Local Edition customer. For assistance with porting or chaining connectors, contact Boomi Support via Boomi Community.
Local Edition Chaining
HTTP Basic Authentication connector natively supports chaining and can be chained with existing Customer Processors as well as Connectors developed and available.
For example, if you want to chain REST - SOAP Transformation Connector with HTTP Basic Authentication Connector, refer to Configuring Endpoint Call Processing (Example of Chaining).
Configuring Endpoint Call Processing (Example of Chaining)
Procedure
-
Sign in to the Boomi Cloud API Management (Control Center) dashboard.
-
Click API Definitions on the Get Started page or navigate to Design > APIs.
-
On the Manage your APIs with API Definitions page, in the Name column, select the API Definition link from the list. This opens the Endpoint Settings:
<your endpoint name>page. -
On the Endpoint:
<your endpoint name>page, in the Name column, select an endpoint link or settings icon next to the row you want to configure endpoint settings. -
Navigate to Call Transformations. On the Call Transformations page, specify the following information in these fields:
-
Processing Adapter:
com.mashery.proxy.customer.generic.http-basic-auth -
Perform Pre-processing: Enabled
-
Data to make available for pre-processing: Enter the following data one per line:
Data processors:com.mashery.proxy.customer.generic.rest-soap-transformation-connectorcom.mashery.proxy.customer.generic.rest-soap-transformation-connector.soap\_protocol:1.1Keep_Mashery_Default_Response_Code:true
-
-
Do not chain the HTTP Basic Authenticator with:
-
com.mashery.proxy.customer.generic.oauth2-shared-token-adapter -
com.mashery.proxy.customer.generic.oauth2-jwt-authenticatorAll three - HTTP Basic Authenticator, OAuth2JWT Authentication Connector and OAuth2 Shared Token Connector - natively support chaining, but they will not work after chaining.
-
-
Do not chain the HTTP Basic Authenticator with:
-
com.mashery.proxy.customer.generic.JWTAuthProcessor -
com.mashery.proxy.customer.generic.oauth-token-validation-connectorAll three - HTTP Basic Authenticator, JWT Authentication Processor and OAuth2.0 Token Authentication Connector - require a token in Authorization header and will not work properly if used simultaneously.
-