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 administrative console page for the server level, complete the following steps:
  1. Click Servers > Server Types > WebSphere application servers > server_name.
  2. Under Security, click JAX-WS and JAX-RPC security runtime.
    Mixed-version environment 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
  3. Under Default Generator Bindings, click Token consumers.

Token consumer name

[Version 6 only]

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.

Token consumer class name

[Version 6 only]

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.




Related tasks
Configuring token consumers using JAX-RPC to protect message authenticity at the server level
Configuring programmatic logins for Java Authentication and Authorization Service
Related reference
Token consumer configuration settings
Token generator collection
Token generator configuration settings
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=uwbs_tokenconsumer
File name: uwbs_tokenconsumer.html