Configuring the security token requirement in consumer security constraints

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 Simple Object Access protocol (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 WAS authenticates the security token and sets up the caller identity on the thread.

Complete the following steps to 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. In the following steps, configure either the client-side extensions in step 2 or the server-side extensions in step 3.

  1. Click Window > Open Perspective > J2EE.

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

    1. Expand the Web Services > Client section and double-click the name of the Web service.

    2. Click the WS Extension tab and expand the Response Consumer Configuration section.

  3. 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:

    1. Expand the Web Services > Services section and double-click the name of the Web service.

    2. Click the Extensions tab and expand the Request Consumer Service Configuration Details section.

  4. Expand the Required Security Token section. The Required Security Token Dialog window is displayed.

  5. Click Add to configure the security token. Complete the following steps to configure the security token:

    1. Specify a name for the security token in the Name field. For example, you might specify un_token.

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

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

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

  6. Click OK to save the configuration changes.

When you configure the token consumer, select the security token that you created using these steps. For more information, see Configuring token consumers with an assembly tool.

 

Related tasks

Configuring token consumers with an assembly tool