Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Token consumer collection
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 admin 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 admin console page for the server level...
- Click Servers > Server Types > WebSphere application servers > 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 Default Generator Bindings, click Token consumers.
To view this admin 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, 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.
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 JAAS Login Module implementation is used to validate (authenticate)
the security token on the consumer side.
Configure token consumers using JAX-RPC to protect message authenticity at the server or cell level
Configure programmatic logins for JAAS
Related
Token consumer configuration settings
Token generator collection
Token generator configuration settings
JAAS configuration settings