View web services client deployment descriptor (JAX-RPC)
View the client deployment descriptor.
This administrative console page applies only to JAX-RPC applications.
Before beginning this task, the web services application must be installed.
By completing this task, we can gather information that enables your to maintain or configure binding information. After the web services application is installed, we can view the web services deployment descriptors.
To view this administrative console page:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name .
- 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 server-level bindings, which are the defaults:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click 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 Security > Web services.
If we are using any of the following configurations, verify that the deployment descriptor is configured properly:
- Request signing
- Request encryption
- BasicAuth authentication
- Identity (ID) Assertion authentication with BasicAuth TrustMode
- Identity (ID) Assertion authentication with the Signature TrustMode
- Response digital signature verification
- Response decryption
Request signing
If the integrity constraints (digital signature) are specified, verify that we configured the signing information in the binding files.
To configure signing parameters:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web Services: Client security bindings.
- In the Response receiver binding column, click Edit > Signing information > New.
To configure the key locators:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click 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 we configured the encryption information in the binding files.
To configure the encryption parameters:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click Edit > Encryption Information > New.
To configure the key locators:
- Click Servers > Server Types > WebSphere application servers > server.
- 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:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- 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:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- Under Request sender bindings, click Edit > Login binding.
Identity (ID) Assertion authentication with the Signature TrustMode
Configure 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:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Additional properties, click security runtime > Login mappings > IDAssertion.
To configure the login binding information:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- Under Request sender bindings, click Edit > Login binding.
Response digital signature verification
If the integrity constraints, which require a signature, are defined, verify that we configured the signing information in the binding files.
To configure signing parameters:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click Edit > Signing information > New.
To configure the trust anchors:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click 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 Trust anchors > New.
To configure the collection certificate store, complete the following steps:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click 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 definedd the encryption information.
To configure the encryption information:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Client security bindings.
- In the Response receiver binding column, click Edit > Encryption information > New.
To configure the key locators:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click 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.