You can specify the security token when you configure the response
consumer or the request consumer. The response consumer is configured for
the client, and the request consumer is configured for the server.
Before you begin
Prior to completing this task, you must import your application into
an assembly tool.
For information on how to import
your application, see Importing
enterprise applications.
About this task
A security token represents a set of claims that are made by a client
and might include a name, password, identity, key, certificate, group, privilege,
and so on. It is embedded in the SOAP message within the SOAP header. WebSphere
Application Server propagates the security token within the SOAP header from
the message sender to the intended message receiver. On the receiving side,
the security handler for WebSphere Application Server authenticates the security
token and sets up the caller identity on the thread.
Complete the following
steps. You must configure either the client-side extensions in step 2 or the
server-side extensions in step 3.
Procedure
- Start the assembly tool.
- Switch to the Java 2 Platform, Enterprise Edition (J2EE) perspective.
Click Window > Open Perspective > J2EE.
- Optional: Locate the client-side extensions using the
Project Explorer window. The Client Deployment Descriptor window
is displayed. This Web service contains the extensions that you need to configure.
Complete the following steps to locate the client-side extensions:
- Expand the Web Services > Client section and double-click
the name of the Web service.
- Click the WS Extension tab and expand the Response Consumer
Configuration section.
- Optional: Locate the server-side extensions using the
Project Explorer window. The Web Services Editor window is displayed.
This Web service contains the extensions that you need to configure. Complete
the following steps to locate the server-side extensions:
- Expand the Web Services > Services section and double-click
the name of the Web service.
- Click the Extensions tab and expand the Request Consumer
Service Configuration Details section.
- Expand the Required Security Token section. The Required
Security Token Dialog window is displayed.
- Click Add to configure the security token. Complete
the following steps to configure the security token:
- Specify a name for the security token in the Name field.
For example, you might specify un_token.
- Select a token type from the Token type field.
For example, if you want to send a username token, select Username for
the token type. If you select a token type other than custom token, you do
not need to specify values in the Uniform Resource Identifier (URI) and Local
name fields. These fields are automatically specified when you select
a token type other than custom token.
For a username token or an X.509
token, you do not need to specify a value in the URI field.
- Optional: Specify a value for the URI and Local
name fields if you are configuring a custom token. For example,
you might specify http://www.ibm.com/custom in the URI field
and CustomToken in the Local name field.
- Specify a usage type in the Usage type field. This
field specifies whether the token must be present in the SOAP message or optional.
The value of this attribute is either Required or Optional.
- Click OK to save the configuration changes.