Configure secure communications with WebSphere Application Server and WebSphere Message Broker using SAML 2.0 tokens and Tivoli Federated Identity Manager
From the developerWorks archives
Date archived: May 5, 2017 | First published: April 13, 2011
This article shows you how to configure secure communication using the SAML token profile with WebSphere Application Server V7 hosting a Web service client and server, and WebSphere Message Broker V7 acting as an enterprise service bus to mediate the application communication and ensure that security requirements are met. IBM Tivoli Federated Identity Manager V6.2 acts as the Security Token Service (STS) and issues the SAML tokens.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.