Token consumer collection
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 cell level:
- Click Security > JAX-WS and JAX-RPC security runtime.
- Under Default Consumer Bindings, click Token consumers.
To view this administrative console page for the server level, 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 Default Generator Bindings, click Token consumers.
To view this administrative console page for v6.x and later applications on the application level:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Click Manage modules > URI_name .
- Under Web Services Security Properties, we 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.
Token consumer name
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.
Token consumer class name
Name of the token consumer implementation class.
This class must implement the com.ibm.wsspi.wssecurity.token.TokenConsumerComponent interface.
Token consumer class name
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.