Creating a required security token for the request message

The third step in implementing basic authentication is to create a required security token for the request message to be received by the export.

Before you create a required security token, you should ensure that you have created a token generator as described in the topic "Creating a token generator for the request message."
To create a required security token:
  1. In the Business Integration view, select the module that contains your Web services export, as shown in the following figure:
    Picture of a server module selected in the Business Integration view
  2. Right-click the selected module and select Open Deployment Editor. The module deployment editor opens.
  3. Click the Export WS-Security tab.
  4. Click the Extensions tab. The Web Services Security Extensions page opens, as shown in the following figure:
    Picture of the Web Services Security Extensions page in the module deployment editor
  5. In the Web Service Description Extension section, select the Web service description extension corresponding to your Web Service export's service name. For example, in the above figure, the Web service description extension ServerInterfaceExport1_ServerInterfaceHttpService is selected.
  6. In the Port Component Binding section, select the port component binding that you want to use for the Web service description extension that you selected. The port component binding comes from the port name of your Web service export. For example, in the above figure, the port component binding receiveWebServiceCallFromClient_ServerInterfaceHttpPort is selected.
  7. Expand the Request Consumer Service Configuration Details section.
  8. Expand the Required Security Token subsection.
  9. Click Add. The Required Security Token dialog box opens.
  10. In the Name field, type a name for the new required security token. For example, reqUNToken.
  11. In the Token type drop-down list, select Username. The Local name field is automatically populated with a default value.
  12. Leave the URI field blank. No URI value is required for a username token.
  13. In the Usage type drop-down list, select Required. The Required usage will cause a SOAP fault to be thrown whenever a required security token is not included in the import's request message. The Required Security Token dialog box should now resemble the following figure:
    Picture of the Required Security Token dialog box
  14. Click OK. The new required security token reqUNToken is displayed, as shown in the following figure:
    Picture of the new required security token reqUNToken
  15. Press Ctrl-S to save your changes.
After you have finished creating a required security token, you need to create a caller part as described in the topic "Creating a caller part for the request message."
Related tasks
Enabling security on the server
Creating a security token for the request message
Creating a token generator for the request message
Creating a caller part for the request message
Creating a token consumer for the request message
Testing authentication using the integration test client
Disabling security on the server

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.