SOAP Binding Service is a transport layer for sending and receiving SOAP messages. In the SOAP Binding Service process, an identity service calls the client side application programming interface to construct a message and send it to the SOAP Receiver servlet (SOAP endpoint). The SOAP Receiver servlet receives the message, verifies the signature, and constructs a second message. The SOAP Receiver servlet then invokes the correct Request Handler to send this second message to the corresponding identity service for a response. The identity service processes the second message, generates a response, and sends that response back to the SOAP Receiver servlet. The servlet, in turn, sends the response back to the identity service for processing.
The following SOAP Binding Service global attributes can be configured for your implementation.
The following task is associated with configuring the SOAP Binding Service:
The Request Handler List stores information about the classes implemented from the com.sun.identity.liberty.ws.soapbinding.RequestHandler interface. The SOAP Binding Service provides the interface to process requests and return responses. It must be implemented on the server side for each Liberty-based web service that uses the SOAP Binding Service.
Currently, the Discovery Service, implemented Data Services Template (DST) services (including the Liberty Personal Profile Service and the sample Employee Profile Service, if deployed), and the Authentication Web Service use the SOAP Binding Service client API.
The Request Handler List displays entries that contain key/value pairs separated by a pipe as in key=disco|class=com.example.identity.liberty.ws.disco.DiscoveryService.
To modify the Request Handler list, see To Configure a Request Handler.
The Request Handler List stores information about the classes implemented from the com.sun.identity.liberty.ws.soapbinding.RequestHandler interface. com.sun.identity.liberty.ws.soapbinding.RequestHandler must be implemented on the server side by each Liberty-based identity service that accesses the SOAP Binding Service.
In the Federation Manager Console, click the Web Services tab.
Under Web Services, select the SOAP Binding Service tab.
Under Request Handler List, click New or Edit to display the Request Handler List attributes.
Provide values for the attributes.
The Key property is the last part of the URI path to a SOAP endpoint. The SOAP endpoint in Federation Manager is the SOAP Receiver servlet. The URI to the SOAP Receiver uses the format protocol://host:port/deloy-uri/Liberty/key. If you define disco as the Key, the URI path to the SOAP endpoint for the corresponding Discovery Service would be protocol://host:port/amserver/Liberty/disco. Different service clients use different keys when connecting to the SOAP Receiver.
The Class property specifies the name of the implemented Request Handler class for the particular web service. For example, class=com.example.identity.liberty.ws.disco.DiscoveryService.
SOAP Action can be used to indicate the intent of the SOAP HTTP request. The SOAP processor on the receiving system can use this information to determine the ultimate destination for the service. The value is a URI. No defined value indicates no intent.
SOAP places no restrictions on the format or specificity of the URI or that it is resolvable.
Click OK to complete the Request Handler configuration.
Click Save on the SOAP Binding Service page to complete the service configuration.
This attribute takes as a value the implementation class for the Web Service Authenticator interface. This class authenticates a request and generates a credential for a web service consumer.
This attribute specifies the authentication mechanisms supported by the SOAP Receiver. Authentication mechanisms offer user authentication, as well as data integrity and encryption. By default, all available authentication mechanisms are selected. If one is not selected, and a web services consumer sends a request using it, the request is rejected. Following is a list of the supported authentication mechanisms: