+

Search Tips   |   Advanced Search

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 administrative console page for the cell level:

  1. Click Security > JAX-WS and JAX-RPC security runtime.

  2. Under JAX-RPC Default Generator Bindings, click Token generators.

To view this administrative console page for the server level, complete the following steps:

  1. Click Servers > Server Types > WebSphere application servers > server.

  2. 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

  3. 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 Java Authentication and Authorization Service (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
  • Token consumer collection
  • Token consumer configuration settings
  • Token generator configuration settings