Configure a WS-Trust V1.3 compliant Security Token Service (STS), such as Tivoli® Federated Identity Manager (TFIM) V6.2, to map the incoming security token and, if required, to authenticate and authorize it.
Before you can configure a message flow to perform identity mapping, you need to check that an appropriate security profile exists, or create a new security profile. For information about security profiles, see Creating a security profile.
To configure TFIM V6.2 to map an incoming security token, you must create a custom module chain in TFIM, which performs the security operations. The TFIM configuration controls the token type that is returned from the mapping.
The security manager invokes the WS-Trust v1.3 provider only once, even if it is set for additional security operations (such as authentication or authorization). As a result, when you are using TFIM V6.2, you must configure a single module chain to perform all the required authentication, mapping, and authorization operations.
When the security profile includes a mapping operation, the STS (for example, TFIM V6.2) must return a security token in its response. The STS can return the original unmodified token if no token exchange is required.
For more information about these parameters, see:Authentication, mapping, and authorization with TFIM V6.2 and TAM .
http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.html
For
information on how to configure TFIM, see the IBM Tivoli Federated
Identity Manager product documentation online.
Follow these steps to enable an existing message flow to perform identity mapping.