You can configure a token consumer for either the client-side bindings or the server-side bindings by using an assembly tool.
For information on how to import your application, see Importing enterprise applications.
A security token represents a set of claims that are made by a client. This set of claims might include a name, password, identity, key, certificate, group, privilege, and so on. A security token is embedded in the SOAP message within the SOAP header. The security token within the SOAP header is propagated 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 running thread.
Complete the following steps to configure a token consumer for either the client-side bindings in step 2 or the server-side bindings in step 3:
In this information ...Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |