Use this page to
view the token consumer. The information
is used on the consumer side only to process the security token.
To view this administrative console page for the server
level,
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
- Under
Default Generator Bindings, click Token consumers.
To view this administrative
console page for Version 6.
x and later applications
on the application level, complete the following steps:
- Click .
- Click .
- Under Web Services Security Properties, you
can access the signing
information for the following bindings:
- For the Response generator
(sender) binding, click Web
services: Server security bindings. Under Response generator
(sender) binding, click Edit custom. Under
Required properties, click Token consumers.
- For the Response consumer (receiver) binding, click Web
services: Client security bindings. Under Response consumer
(receiver) binding, click Edit custom. Under
Required properties, click Token consumers.
Specifies the name of the token consumer
configuration.
For example, the default X509 token consumer names can be either con_enctcon for
encrypting or con_signtcon for signing. Or
a custom token consumer name might be sig_tcon for
signing.
Specifies the name of the token consumer implementation
class.
This class must implement the com.ibm.wsspi.wssecurity.token.TokenConsumerComponent interface.
Specifies the name of the token
consumer implementation
class.
The Java Authentication
and Authorization Service
(JAAS) Login Module implementation is used to validate (authenticate)
the security token on the consumer side.