Configure the server security bindings using an assembly tool
Configure the server security bindings using an assembly tool
Important distinction between Version 5.x and Version 6 applications
Note: The information in this article supports version 5.x applications only that are used with WebSphere Application Server Version 6. The information does not apply to version 6 applications.
Create an Enterprise
JavaBean (EJB) file Java archive (JAR) file or a Web archive (WAR) file containing the security binding file (ibm-webservices-bnd.xmi) and the security extension file (ibm-webservices-ext.xmi). If this archive is acting as a client to a downstream service, you also need the client-side binding file (ibm-webservicesclient-bnd.xmi) and the client-side extension file (ibm-webservicesclient-ext.xmi). These files are generated using the WSDL2Java command. You can edit these files using the Web services editor in the Assembly tools.
When configuring server-side security for Web services security,
the security extensions configuration specifies what security is performed,
the security bindings configuration indicates how to perform what is specified in the security extensions configuration. You can use the defaults for some elements at the cell and server levels in the bindings configuration,
including key locators, trust anchors, the collection certificate store, trusted ID evaluators, and login mappings and reference these elements from the WAR
and JAR binding configurations.
Prior to importing the Web services
enterprise archive (EAR) file into the assembly tool, make sure that you have already run the wsdl2java command on your Web service to enable your J2EE application. You must import the Web services enterprise archive (EAR)
file into the assembly tool.
Open the Web services editor in an assembly tool to begin editing the server security extensions and bindings.
The following steps can locate the server security extensions and bindings.
Other tasks specify how to configure each section of the extensions and bindings in more detail.
Launch an assembly tool. For more information on the assembly tools, see Assembly tools.
Click Windows > Open perspective > Other > J2EE .
Configure the server for inbound requests and outbound responses security configuration. To configure the server for inbound requests and outbound responses, complete the following steps:
Right-click the webservices.xml file and click Open with > Web services editor . The webservices.xml file represents the server-side (inbound) Web services configuration. The webservicesclient.xml file represents the client-side (outbound) Web services configuration.
In the Web services editor (for the webservices.xml file and inbound requests and outbound responses Web services configuration), there are several tabs at the bottom of the editor including Web Services, Port Components, Handlers, Security Extensions, Bindings, and Binding Configurations.
The security extensions are edited using the Security Extensions tab. The security bindings are edited using the Security Bindings tab.
Click the WS Extensions tab and select the port component binding to edit. The Web services security extensions are configured for inbound requests and outbound responses. You need to configure the following information for
Web services security extensions. These topics are discussed in more detail in other topics in the documentation. Request receiver service configuration details
Click the Binding Configurations tab and select the port component binding to edit. The Web services security bindings are configured for inbound requests and outbound responses. You need to configure the following information for Web services security bindings. These topics are discussed in more details in other topics in the documentation.
Response receiver binding configuration details
Configure the client for outbound requests and inbound responses security configuration by right-clicking the webservicesclient.xml file and clicking Open With > Deployment descriptor editor . For more information,
see Configuring the client security bindings using an assembly tool.