Sun Java System Identity Server 2004Q2 Administration Guide |
Chapter 40
SOAP Binding Service AttributesThe SOAP Binding Service attributes are global attributes. The values applied to them are carried across the Sun Java System Identity Server configuration and inherited by every configured organization. (They can not be applied directly to roles or organizations as the goal of global attributes is to customize the Identity Server application.)
The SOAP Binding Service attributes are as follows:
Request Handler List
This attribute stores information about a Web Service Provider (WSP) deployed in Identity Server. It lists entries that contain a key/value pair (separated by “|”). For example:
key=disco|class=com.example.identity.liberty.ws.disco.DiscoveryService|soa pActions=sa1 sa2 sa2
To add a new request handler, click the add button. The key and class parameters are required. The parameters are:
key. This defines the second part of the URI path for the SOAP endpoint of the WSP. The first part is defined as Liberty by the SOAP services. For example, if you define disco as the key, the SOAP endpoint for the Discovery service is:
protocol://hostname:port/deloy_uri/Liberty/disco
class. This parameter specifies the name of the implementation class for the WSP. The Liberty SOAP layer provides a handler interface to be implemented by each WSP to process the requested message and then return a response.
soapActions. This is an optional parameter that specifies supported SOAPActions. If this parameter is not specified, all SOAPActions are supported. If a Web Service Consumer (WSC) sends a request with an unsupported SOAPAction, the request will be rejected by the SOAP layer without passing it one to the corresponding WSP.
Web Service Authenticator
This attribute defines the implementation class for the WebServiceAuthenicator interface, which authenticates and generates a credential for a Web Service Consumer (WSC), based on the request.
Supported Authentication Mechanisms
This attribute specifies the authentication mechanisms supported by the SOAP endpoint. By default, all of the mechanisms are selected. If an authentication mechanism is not selected, and a WSC sends a request using that authentication mechanism, the request will be rejected by the SOAP layer without passing it to the corresponding WSP.