View web services client deployment descriptor
Use this page to view your client deployment descriptor.
This administrative console page applies only to Java™ API for XML-based RPC (JAX-RPC) applications.
Before you begin this task, the web services application must be installed.
By completing this task, you can gather information that enables your to maintain or configure binding information. After the web services application is installed, you can view the web services deployment descriptors.
- Click .
- Under Modules, click .
- Under Web Services Properties, click View web services client deployment descriptor extension.
The information in the following implementation indicates how to configure your application-level bindings. If the web server is acting as a client, the default bindings are used. To configure the server-level bindings, which are the defaults, complete the following steps:
- Click .
- Under Security, click JAX-WS and JAX-RPC security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv
- To configure the cell-level bindings, click .
Request signing
If the integrity constraints (digital signature) are specified, verify that you configured the signing information in the binding files.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web Services: Client security bindings.
- In the Response receiver binding column, click .
- Click .
- Under Security, click JAX-WS and JAX-RPC security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv
- Under Additional properties, click Key locators.
Request encryption
If the confidentiality constraints (encryption) are specified, verify that you configured the encryption information in the binding files.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click .
- Click .
- Under Additional properties, click Web Services: Default bindings for Web Services Security > Key locators.
BasicAuth authentication
- This implementation prompts for basic authentication information, the user name and password, in an interface.
- This implementation reads the basic authentication information from the binding file.
- This implementation prompts for a user name and password using the standard in (stdin) prompt.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- Under Request sender bindings, click .
Identity (ID) Assertion authentication with BasicAuth TrustMode
Configure a login binding in the bindings file with a com.ibm.wsspi.wssecurity.auth.callback.NonPromptCallbackHandler implementation. Specify a BasicAuth user name and password that a trusted ID evaluator on a downstream server trusts.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- Under Request sender bindings, click .
Identity (ID) Assertion authentication with the Signature TrustMode
Configure the signing information in the bindings file with a signing key pointing to a key locator. The key locator contains the X.509 certificate that is trusted by the downstream server.
- Click .
- Under Additional properties, click .
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- Under Request sender bindings, click .
Response digital signature verification
If the integrity constraints, which require a signature, are defined, verify that you configured the signing information in the binding files.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click .
- Click .
- Under Security, click JAX-WS and JAX-RPC security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv
- Under Additional properties, click .
- Click .
- Under Security, click JAX-WS and JAX-RPC security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv
- Under Additional properties, click Collection certificate store > New.
Response decryption
If the confidentiality constraints (encryption) are specified, verify that you defined the encryption information.
- Click .
- Under Modules, click .
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click .
- Click .
- Under Security, click JAX-WS and JAX-RPC security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv
- Under Additional properties, click Key locators.