Configure the server security bindings using the administrative console
Use the WebSphere Application Server administrative console to edit bindings for a web service after these bindings are deployed on a server.
Create an EJB file Java archive (JAR) file or web application 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. See the WSDL2Java command for JAX-RPC applications. We can edit these files using the Web Services Editor in the assembly tools. See assembly tools.
When configuring server-side security for Web Services Security, the security extensions configuration specifies what security is to be performed while the security bindings configuration indicates how to perform what is specified in the security extensions configuration. 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 them from the WAR and JAR binding configurations.
The following steps describe how to edit bindings for a web service after these bindings are deployed on a server. When one web service communicates with another web service, you also must configure the client bindings to access the downstream web service.
Tasks
- Access the administrative console:
http://localhost:port_number/ibm/console.
After you log into the administration console, click...
Applications > Install new application to deploy the web service. See installing enterprise application files with the console.
- After we deploy the web service, click...
Applications > Enterprise applications > application_name .
- Under Manage modules, click URI_name.
- Under Web Services Security Properties, click Web services: client security bindings for outbound requests and inbound responses. Click Web services: server security bindings for inbound requests and outbound responses.
- If we click Web services: server security bindings, the following sections can be configured. These topics are discussed in more detail in other sections of the documentation.
- Request receiver binding
- Signing information
- Encryption information
- Trust anchors
- Collection certificate store
- Key locator
- Trusted ID evaluator
- Login mappings
- Response sender binding
- Signing parameters
- Encryption information
- Key locator
Related:
Development and assembly tools Secure web services for v5.x applications using XML digital signature Configure the client security bindings using an assembly tool Configure the security bindings on a server acting as a client Configure the server security bindings using an assembly tool Install enterprise application files with the console WSDL2Java command for JAX-RPC applications