Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Token generator collection
Use this page to view the token generators. The information is used on the generator side only to generate the security token.
To view this admin console page for the cell level...
- Click Security > JAX-WS and JAX-RPC security runtime.
- Under JAX-RPC Default Generator Bindings, click Token generators.
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 JAX-RPC Default Generator Bindings, click Token generators.
Token generator name
Name of the token generator configuration.
For example, the default X509 token generator names are either gen_enctgen for encrypting or gen_signtgen for signing. Or a custom token generator name might be sig_tgen for signing.
Token generator class name
Name of the token generator implementation class.
This class must implement the com.ibm.wsspi.wssecurity.token.TokenGeneratorComponent interface.
Token generator class name
Name of the token generator implementation class.
The JAAS Login Module implementation is used to create the security token on the generator side.
Configure token generators using JAX-RPC to protect message authenticity at the server or cell level
Configure programmatic logins for JAAS
Related
Token consumer collection
Token consumer configuration settings
Token generator configuration settings