Configuring Endpoint Call Processing as a Processor

note

When the Authorization header is missing in the API request or credentials are not present in this header with the Basic scheme:

Configuring the Connector as Processor overrides the default behavior of the Cloud API Management Proxy server and results in a 403 response code.
Since the default behavior of responding with a 401 code is closer to RFC guidelines, this configuration is the recommended approach.

For configuring endpoint call processing as a Processor:

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:

Pre-Input Data Example Notes

Pre-Input Data	Example	Notes
`Keep_Mashery_Default_Response_Code : <true/false>`	`Keep_Mashery_Default_Response_Code:true`	This is an optional field. Default value: `false` Note: This check is case insensitive. Example of valid values - `true`, `TRUE`, `True`, `true`, etc. In case this parameter is not specified or specified as empty or any other string other than case insensitive boolean true, then its value will be considered as false. For backward compatibility if any customer expects Cloud API Management platform default behavior to return `403` response if Authorization header is not present in the request or credentials are not present in this header with Basic scheme, then `Keep_Mashery_Default_Response_Code` pre-input parameter can be configured as `"true"`.

Keep_Mashery_Default_Response_Code : <true/false>

Keep_Mashery_Default_Response_Code:true

This is an optional field.

Default value: false

Note: This check is case insensitive.

Example of valid values - true, TRUE, True, true, etc.

In case this parameter is not specified or specified as empty or any other string other than case insensitive boolean true, then its value will be considered as false.

For backward compatibility if any customer expects Cloud API Management platform default behavior to return 403 response if Authorization header is not present in the request or credentials are not present in this header with Basic scheme, then Keep_Mashery_Default_Response_Code pre-input parameter can be configured as "true".

Click Save.