+

Search Tips   |   Advanced Search

View Web services client deployment descriptor

Use this page to view your client deployment descriptor.

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. To view this console page...

  1. Click Applications > Enterprise applications > application.

  2. Under Related Items, click EJB modules or Web modules > URI_file_name .

  3. Under Additional properties, click View Web services client deployment descriptor extension.

Application-level, server-level, and cell-level are the three levels of bindings that WAS Network Deployment offers. The information in the following implementation descriptions 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...

  1. Click Servers > Application servers > server_name.

  2. Under Security, click Web Services: Default bindings for Web services security.

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

If you are using 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, complete the following steps:

  1. Click Applications > Enterprise applications > application.

  2. Under Related Items, click Web modules > URI_file_name

  3. Under Additional properties, 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 > Application servers > server.

  2. Under Additional properties, click Web Services: Default bindings for Web services security > 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, complete the following steps:

  1. Click Applications > Enterprise applications > application.

  2. Under Related Items, click EJB modules or Web modules > URI_file_name > Web services: Client security bindings .

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

To configure the key locators...

  1. Click Servers > Application servers > server.

  2. Under Additional properties, click Web Services: Default bindings for Web services 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, complete the following steps:

  1. Click Applications > Enterprise applications > application.

  2. Under Related items, click EJB modules or Web modules > URI_file_name > Web services: Client security bindings.

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

 

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

  1. Click Applications > Enterprise applications > application.

  2. Under Related items, click EJB modules or Web modules > URI_file_name > Web services: Client security bindings.

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

 

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

  1. Click Servers > Application servers > server.

  2. Under Additional properties, click Web services: Default bindings for Web services security > Login mappings > IDAssertion.

To configure the login binding information, complete the following steps:

  1. Click Applications > Enterprise applications > application.

  2. Under Related items, click EJB modules or Web modules > URI_file_name > Web services: Client security bindings.

  3. 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 > Enterprise applications > application.

  2. Under Related Items, click EJB modules or Web modules > URI_file_name > Web services: Client security bindings.

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

To configure the trust anchors...

  1. Click Servers > Application servers > server.

  2. Under Additional properties, click Web Services: Default bindings for Web services security > Trust anchors > New.

To configure the collection certificate store, complete the following steps:

  1. Click Servers > Application servers > server.

  2. Under Additional properties, click Web Services: Default bindings for Web services security > 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, complete the following steps:

  1. Click Applications > Enterprise applications > application.

  2. Click Manage modules > URI_file_name > Web services: Client security bindings.

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

To configure the key locators...

  1. Click Servers > Application servers > server.

  2. Under Additional properties, click Web Services: Default bindings for Web services security > Key locators.



 

Related tasks


Migrating V5.x applications with Web services security to V6.1 applications

 

Related Reference

View Web services server deployment descriptor

 

Reference topic