Using the HTTP Binding Component

Web Service Client Calling an Operation Using HTTP Basic Authentication

In this example, a client invokes a service that requires HTTP Basic Authentication. This example assumes that you are running a deployed BPEL project with a WSDL configured to handle HTTP Basic Authentication. This BPEL project invokes a service protected using HTTP Basic Authentication.

Results

The service processes the expected SOAP Message through HTTP after verifying the security credentials.

Main Scenario

  1. A web service client invokes an in-only abstract operation that is implemented by a BPEL process. The abstract operation has a concrete HTTP SOAP binding, so the client must use SOAP over HTTP protocol to properly invoke the operation.

  2. The BPEL Process, acting as the client, receives the message for the abstract operation and invokes a different in-only abstract operation. This operation has a concrete HTTP SOAP binding that requires HTTP Basic Authentication.

  3. The binding component picks up the normalized message and converts it to a SOAP message.

  4. The binding component pulls the appropriate username and password from the Access Manager or from the WSDL.

  5. The binding component forwards the message and proper security credentials to the service.