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.
To view this administrative console page, complete the following
steps:
- Click .
- 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
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 server_name.
- 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
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:
- Click .
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security propertiess, click Web Services:
Client
security bindings.
- In the Response receiver binding column,
click Edit > Signing
information > New.
To configure the
key locators, complete the following steps:
- Click server_name.
- 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.
To configure the encryption
parameters,
complete the following steps:
- Click .
- Under Modules, click .
- 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, complete the following steps:
- Click server_name.
- 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 .
- Under Modules, click .
- 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,
complete the following steps:
- Click .
- Under Modules, click .
- 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 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, complete the following steps:
- Click server_name.
- Under Additional properties, click JAX-WS and JAX-RPC
security
runtime > Login mappings > IDAssertion.
To
configure the login binding information, complete the following
steps:
- Click .
- Under Modules, click .
- 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 you configured the signing information in the binding files.
To
configure the signing parameters, complete the following steps:
- Click .
- Under Modules, click .
- 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, complete the following steps:
- Click server_name.
- 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 Trust anchors > New.
To configure the collection certificate store, complete
the following
steps:
- Click server_name.
- 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.
To configure the encryption information, complete
the following
steps:
- Click .
- Under Modules, click .
- 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, complete the following steps:
- Click server_name.
- 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.