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 cell level, complete the following steps:
- Click Security > Web services.
- Under Default consumer bindings, click Token consumers.
To view this administrative console page for the server level, complete
the following steps:
- Click Servers > Application servers > server_name .
- Under Security, click Web services: Default bindings for Web services
security.
- Under Default generator bindings, click Token consumers.
To view this administrative
console page for Version 6 and later applications on the application level,
complete the following steps:
- Click Applications > 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.
Specifies the name of the token consumer configuration.
newfeatFor 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.
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.