See information about the latest product version
Configuring authorization with TFIM V6.1
You can configure a message flow to perform authorization on an identity by using Tivoli® Federated Identity Manager (TFIM) V6.1.
Before you start:
- Check that an appropriate security profile exists, or create a new security profile. See Creating a security profile for TFIM V6.1.
- Define the required users and groups in TFIM.
- Issuer = Properties.IdentitySourceIssuedBy
- Applies To = The Fully Qualified Name of the Flow: <Brokername>.<Execution Group Name>.<Message Flow Name>
- Token = Properties.IdentitySourceToken
Authorization is performed with TFIM using an instance of the TFIM AuthorizationSTSModule in the selected module chain. The TFIM AuthorizationSTSModule must be set with Mode = Other. This AuthorizationSTSModule authorizes a user by checking an Access Control List (ACL) from Tivoli Access Manager (TAM). TFIM performs the authorization check by verifying that the action "i" (invoke) has been granted in an ACL for the WebService action group.
The ACL is found starting from the root of the TAM object space using a path formed from the Authorization module Web service protected object name parameter, followed by the Port Type and Operation Name from the authorization request. When the broker makes an authorization request to TFIM, the Port Type and Operation Name parameters have the following values:
- PortType:<Message flow name>
- Operation "MessageFlowAccess"
Therefore, the ACL is found at this location in the TAM object space:
/<WSProtectedObjectName>.<MessageFlowName>."MessageFlowAccess"
For more information about this process and the parameters, see Authentication, mapping, and authorization with TFIM V6.1 and TAM.
Steps for enabling TFIM authorization:
- Switch to the Broker Application Development perspective.
- In the Broker Development view, right-click the BAR file, then click Open with > Broker Archive Editor.
- Click the Manage and Configure tab.
- Click the flow or node on which you want to set the security profile. The properties that you can configure for the message flow or for the node are displayed in the Properties view.
- In the Security Profile Name field, select a security profile that has authorization enabled.
- Save the BAR file.
For a SOAPInput node to use the identity in the WS-Security header (rather than an underlying transport identity) an appropriate policy set and bindings must also be defined and specified. For more information, see Policy sets.
For further information on how to configure TFIM, see the IBM® Tivoli Federated Identity Manager Information Center.