1. Using the SOAP Adapter with Oracle Integration Generation 2
  2. Implement Common Patterns Using the SOAP Adapter
  3. Invoke a SOAP Endpoint with an Explicit Authorization Header

Invoke a SOAP Endpoint with an Explicit Authorization Header

For the Basic Authentication security policy, the runtime message includes an Authorization HTTP header with a BASIC mechanism only (for example, Authorization: Basic base64_content_of_credentials).

The authorization header can be overridden in the mapper under Connectivity Properties > Security Properties > Authorization in the outbound request mapping to pass dynamic credentials. However, this header also restricts use to the BASIC mechanism only.

To support a different mechanism such as the BEARER mechanism (for OAuth or JWT token) in the outbound direction, the Authorization HTTP header is enabled in the SOAP Adapter Request-Headers page. Perform the following steps to enable this support.

  1. Create a SOAP Adapter connection.
  2. Select No Security Policy.
  3. Configure the SOAP Adapter as an invoke connection in your integration.
    1. Select Yes for Configure Headers on the Headers page.
    2. Select the Standard HTTP Headers checkbox in the Request Headers section.
    3. Click + to enable the header list on the Request-Headers page.
    4. Select the Authorization header.
      Request Headers page is displayed to show the Standard HTTP Headers tab, which includes a Detach button, Add icon, and Delete icon. Below this is the list of HTTP Header Names.

  4. Complete adapter configuration.
  5. Open the mapper.

    The Authorization HTTP header is visible under the Headers > HTTPHeaders section of the request mapping. Use this to pass any value to the target endpoint.


    Mapper shows the Headers > HTTPHeaders > Authorization element. Below this is the ConnectivityProperties > EndpointProperties section, which includes the EndpointURI and SoapAction elements.