+

Search Tips   |   Advanced Search

View Web services client deployment descriptor


To view the client deployment descriptor.

This admin console panel applies only to Java™ API for XML-based RPC (JAX-RPC) applications.

Before beginning this task, the Web services application must be installed.

By completing this task, we can gather information that enables the to maintain or configure binding information. After the Web services application is installed, we can view the Web services deployment descriptors.

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name .

  3. Under Web Services Properties, click View Web services client deployment descriptor extension.

The information in the following implementation indicates how to configure the 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...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for WS-Security

  3. To configure the cell-level bindings, click Security > Web services.

For any of the following configurations, verify that the deployment descriptor is configured properly:

 

Request signing

If the integrity constraints (digital signature) are specified, verify that you configured the signing information in the binding files. To configure the signing parameters...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security propertiess, click Web Services: Client security bindings.

  4. In the Response receiver binding column, click Edit > Signing information > New.

To configure the key locators...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for WS-Security

  3. 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. To configure the encryption parameters...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. In the Response receiver binding column, click Edit > Encryption Information > New.

To configure the key locators...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Additional properties, click Web Services: Default bindings for WS-Security > Key locators.

 

BasicAuth authentication

If BasicAuth authentication is configured as the required security token, specify the callback handler in the binding file to collect the basic authentication data.

The following list contains the CallBack support implementations:

com.ibm.wsspi.wssecurity.auth.callback.GuiPromptCallbackHandler

This implementation prompts for basic authentication information, the user name and password, in an interface.

com.ibm.wsspi.wssecurity.auth.callback.NonPromptCallbackHandler

This implementation reads the basic authentication information from the binding file.

com.ibm.wsspi.wssecurity.auth.callback.StdPromptCallbackHandler

This implementation prompts for a user name and password using the standard in (stdin) prompt.

To configure the login binding information...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. Under Request sender bindings, click Edit > Login binding.

 

Identity (ID) Assertion authentication with BasicAuth TrustMode

Set 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. To configure the login binding information...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. Under Request sender bindings, click Edit > Login binding.

 

Identity (ID) Assertion authentication with the Signature TrustMode

Set 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. To configure ID assertion...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Additional properties, click JAX-WS and JAX-RPC security runtime > Login mappings > IDAssertion.

To configure the login binding information...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. Under Request sender bindings, click Edit > Login binding.

 

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. To configure the signing parameters...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. In the Response receiver binding column, click Edit > Signing information > New.

To configure the trust anchors...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for WS-Security

  3. Under Additional properties, click Trust anchors > New.

To configure the collection certificate store...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for WS-Security

  3. Under Additional properties, click Collection certificate store > New.

 

Response decryption

If the confidentiality constraints (encryption) are specified, verify that you defined the encryption information. To configure the encryption information...

  1. Click Applications > Application Types > WebSphere enterprise apps > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under WS-Security properties, click Web services: Client security bindings.

  4. In the Response receiver binding column, click Edit > Encryption information > New.

To configure the key locators...

  1. Click Servers > Server Types > WebSphere application servers > server_name.

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for WS-Security

  3. Under Additional properties, click Key locators.




 

Related tasks


Migrate JAX-RPC WS-Security applications to V7.0 applications

 

Related


View Web services server deployment descriptor